feat(transloco): 🎸 auto-detect public folder in ng-add #879
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The ng-add schematic hardcodes the translation files path to
assets/i18n/, which doesn't work properly with Angular 18+ projects that use the newpublic/folder structure instead ofsrc/assets/.Issue Number: #818
What is the new behavior?
The ng-add schematic now automatically detects whether to use
public/i18n/orassets/i18n/based on:/publicor${sourceRoot}/assetsexistspublic/)--pathparameter if providedThis ensures translation files are placed in the correct location and the HTTP loader uses the right URL path for both modern and legacy Angular projects.
Does this PR introduce a breaking change?
Other information
The implementation maintains full backward compatibility while adding intelligent detection for Angular 18+ projects. All existing projects continue to work as before, while new Angular 18+ projects automatically get the correct
public/folder configuration.