-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue 104 #127
base: master
Are you sure you want to change the base?
Fix issue 104 #127
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ces commentaires sont autant pour moi que pour Nicolas Kieffer, ils m'ont permis de revenir dans le code.
export const removeQuote = replace(/'/g, ' '); | ||
/** | ||
* Deplete string from accents, upper case, dash and simple quotes. | ||
* @param {string} str | ||
* @returns {string} | ||
* @private | ||
*/ | ||
export const depleteString = compose(toLower, removeAccents, removeQuote, removeDash, String); | ||
export const depleteString = compose(toLower, removeQuote, removeDash, removeAccents, String); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ça peut être dû à un encodage contenant un tiret (que removeDash
supprime), donc pourquoi pas?
Replaced arr with indexes in contain.
target has not to be sorted, its tokens' order is important, though.
isIn takes only one argument, the second was thus useless.
Add the types, and clarify comment.
It was not taking into account the longer labels or numeros.
Use the previous hasSigle, to prevent false positives.
Tant qu'on n'aura pas précisé le but de cette intervention, ce n'est pas la peine d'intégrer cette Pull Request dans la branche master: il ne reste qu'une modification mineure, qui ne change rien aux tests. |
This is a Pull Request to integrate the fix-issue-104 branch into the master branch.
It was intended to fix #104, but the issue does not contain any description of the problem.
Nor does the branch add or modify a test, so it's hard to know what has to be fixed.