Feat/add context matcher and export types #39
Merged
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.
Hi, this PR adds a new option
translationContextMatcher
.It's purpose is to not split every key up by the
contextSeperator
, but only remove context suffixes.In my code base it made the result of the CLI unusable since the keys are snaked case.
Example:
The
translationContextMatcher
defaults to a regex that should capture the context used by i18n-next in the various versions of their JSON Format. I wasn't sure if anything else existed out there, so I made it configurable.Besides that I've moved some of the documentation from the README into the
RunOptions
interface and exported it, allowing users to have autocomplete when creating their config.I also moved this part
[...matchKeysSet].toString()
out of the for loop, since it seemed unnecessary to compute the string every iteration.Let me know if you have any comments.