fix(@angular-devkit/build-angular): augment base HREF when localizing#16332
Merged
dgp1130 merged 3 commits intoangular:masterfrom Dec 4, 2019
Merged
fix(@angular-devkit/build-angular): augment base HREF when localizing#16332dgp1130 merged 3 commits intoangular:masterfrom
dgp1130 merged 3 commits intoangular:masterfrom
Conversation
clydin
added
state: blocked
target: patch
clydin
force-pushed
the
i18n-basehref-2
branch
from
c9ef2be to
78217d9
Compare
All locale i18n options now support an object form which allows a base HREF to be defined for the locale. Each locale can now optionally define a custom base HREF that will be combined with the base HREF defined for the build configuration. By default if the shorthand form for the locale is used or the field is not present in the longhand form, the locale code will be used as the base HREF. To disable automatic augmentation a base HREF value of an empty string (`""`) can be used. This will prevent anything from being added to the existing base HREF. For common scenarios, the shorthand form will result in the preferred and recommended outcome of each built locale variant of the application containing a defined base HREF containing the locale code.
clydin
force-pushed
the
i18n-basehref-2
branch
from
a3a1023 to
f71d2ab
Compare
Contributor
|
I wonder if the default base HREF could be in some way computed from the |
clydin
force-pushed
the
i18n-basehref-2
branch
from
f71d2ab to
8b4aa9a
Compare
… direct localize usage
Collaborator
|
Merged all 3 commits to v9.0.x patch branch. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
All locale i18n options now support an object form which allows a base HREF to be defined for the locale. This allows each locale to optionally define a custom base HREF that will be combined with the base HREF defined for the build configuration.
By default if the shorthand form for the locale is used or the field is not present in the longhand form, the locale code will be used as the base HREF. To disable automatic augmentation, a base HREF value of an empty string (
"") can be used. This will prevent anything from being added to the existing base HREF.For common scenarios, the shorthand form will result in the preferred and recommended outcome of each built locale variant of the application having a defined base HREF containing the locale code.
Closes #16301