Skip to content

Single assets folder with Angular Internationalization #28027

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

Closed
rbalet opened this issue Jul 10, 2024 · 2 comments
Closed

Single assets folder with Angular Internationalization #28027

rbalet opened this issue Jul 10, 2024 · 2 comments

Comments

@rbalet
Copy link

rbalet commented Jul 10, 2024

Which @angular/* package(s) are relevant/related to the feature request?

localize

Description

Being able to upload only one single assets folder to the server to avoid uploading x time the same image

Proposed solution

I'd say it could be like that by default, and then, instead of writing ../assets we'd be writing /assets.

Then, maybe in the build object, we could add an assetsPath: string which, when given assetsPath: /$localize would then upload the assets to all the localize element

Note

I don't understand why the assets is uploaded multiple time, search over on the internet and couldn't find the reason why, so maybe the issue does not make any sense.

Alternatives considered

@JeanMeche JeanMeche transferred this issue from angular/angular Jul 10, 2024
@clydin
Copy link
Member

clydin commented Jul 10, 2024

Duplicate of #26286

@clydin clydin marked this as a duplicate of #26286 Jul 10, 2024
@clydin clydin closed this as completed Jul 10, 2024
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Aug 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants