Custom prefixes #70
Merged
Custom prefixes #70
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
… prefix only for the URLs
… repo with support for PHP 7.1+
|
Looks great! Thanks! |
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.
Adds backwards compatible support for custom prefixes. This aims to cover one part of #20.
I've used the term "custom prefixes" instead of "slugs" as the latter is used elsewhere in the codebase to reference parts of the path that get localized.
The approach is to preserve the route name prefix as the application locale, and to modify the URL generators to use a custom prefix, if provided.
If custom prefixes are not set, or there is not a custom prefix for any specific locale, the locale string itself is used.