-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(localization): path generated in the angular.json in case of monorepo #2378
Conversation
@@ -98,12 +100,12 @@ export function updateLocalization(options: { projectName?: string | null | unde | |||
locales: [ | |||
'en-GB' | |||
], | |||
assets: [`${mainAssetsFolder}/locales`], | |||
outputPath: `${devResourcesFolder}/localizations` | |||
assets: [`${projectBasePath}/${mainAssetsFolder}/locales`], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't we add a test somewhere to be sure we will not remove that fix at some point ? or understand if we should supports both cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not have e2e for an application outside of the mono-repo.
I can add a UT only.
Edit: The UT of it would require too many changes (due embedded functions). I open the issue #2381 to follow it.
Path generated in the angular.json in case of monorepo.
Proposed change
Related issues
- No issue associated -