Fixed hash generation for common toponym id legacy #414
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
When exporting data from postgresql (main database) to mongodb (exploitation database), we generate legacy ids for common toponym. In the case we cannot find a fantoir code or if the fantoir code is already used on another common toponym, we generate a pseudo code. If the pseudo code is also already used, we generate a hash base on the ban id.
Enhancement
This PR fix :
createHmac
method (fromnode:crypto
) by adding a mandatory 'secret'.