Add the ability to customize the context locale #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to issue #8.
Quick overview (taken from the updated README):
contextLocaleType:
function| Default: (page, config) => get(page, 'url', '').split('/')[1]You might provide a function in order to compute the context locale (that is, the locale applied to the
i18nfilter when no arguments are provided). By default, this would be the first segment of the URL (/en/,/it/and so on). If you use a custom directory strategy, like not prefixing the current locale, this option comes to help. The first argument of the function is thepageobject (could beundefined), the second is the pluginconfigobject.