feat(@angular/build): add support for customizing URL segments with i18n #29011
+273
−32
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
alan-agius4
added
the
target: minor
angular-robot
bot
added
detected: feature
alan-agius4
force-pushed
the
ssr-i18n-output-path
branch
4 times, most recently
from
048d91a
to
8e596e9
Compare
Previously, the `baseHref` option under each locale allowed for generating a unique base href for specific locales. However, users were still required to handle file organization manually, and `baseHref` appeared to be primarily designed for this purpose.
This commit introduces a new `urlSegment` option, which simplifies the i18n process, particularly in static site generation (SSG) and server-side rendering (SSR). When the `urlSegment` option is used, the `baseHref` is ignored. Instead, the `urlSegment` serves as both the base href and the name of the directory containing the localized version of the app.
### Configuration Example
Below is an example configuration showcasing the use of `urlSegment`:
```json
"i18n": {
"sourceLocale": {
"code": "en-US",
"urlSegment": ""
},
"locales": {
"fr-BE": {
"urlSegment": "fr",
"translation": "src/i18n/messages.fr-BE.xlf"
},
"de-BE": {
"urlSegment": "de",
"translation": "src/i18n/messages.de-BE.xlf"
}
}
}
```
### Example Directory Structure
The following tree structure demonstrates how the `urlSegment` organizes localized build output:
```
dist/
├── app/
│ └── browser/ # Default locale, accessible at `/`
│ ├── fr/ # Locale for `fr-BE`, accessible at `/fr`
│ └── de/ # Locale for `de-BE`, accessible at `/de`
```
Closes angular#16997 and closes angular#28967
alan-agius4
force-pushed
the
ssr-i18n-output-path
branch
from
8e596e9
to
5565ae4
Compare
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.
Previously, the
baseHrefoption under each locale allowed for generating a unique base href for specific locales. However, users were still required to handle file organization manually, andbaseHrefappeared to be primarily designed for this purpose.This commit introduces a new
urlSegmentoption, which simplifies the i18n process, particularly in static site generation (SSG) and server-side rendering (SSR). When theurlSegmentoption is used, thebaseHrefis ignored. Instead, theurlSegmentserves as both the base href and the name of the directory containing the localized version of the app.Configuration Example
Below is an example configuration showcasing the use of
urlSegment:Example Directory Structure
The following tree structure demonstrates how the
urlSegmentorganizes localized build output:Closes #16997 and closes #28967