Refactor locale route handling with prefix logic #21
Conversation
This file contains hidden or 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.
This pull request updates the logic for generating localized routes to provide more flexibility in whether the default locale uses a URL prefix. The main change is the introduction of a configuration option that controls if the default locale should have a URL prefix, making route generation more customizable.
Routing behavior improvements:
makeTransRouteForLocaleinsrc/Localize/TransRoute.phpto use thetranslatable.default_locale_url_prefixconfig value to determine if the locale prefix should be used for the default locale, allowing developers to control whether the default locale appears in URLs. By default this will still be the case.