Skip to content

nf: Angular I18n support #456

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

Conversation

refactorTractor
Copy link

@refactorTractor refactorTractor commented Feb 1, 2024

closes #413

Angular i18n support in native federation

This is how i18n support could play out in my opinion:

  • Shared entries/packages build just as they used to.
  • Exposed entries are built by the angular application internal builder
  • index.html-s are found in the build output, and each transformed
  • remoteEntries are copied next to index.html-s found, and transformed for the new directory structure

There is no need to modify the nf-core project (or the runtime)

@refactorTractor refactorTractor changed the title I18n application adapter nf: Angular I18n support Feb 1, 2024
refactorTractor and others added 26 commits February 2, 2024 09:27
…ntry direct, filter polyfills for index.html
@refactorTractor
Copy link
Author

I will use another branch for merging to this repo

@refactorTractor refactorTractor deleted the i18n_application_adapter branch August 23, 2024 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Native federation: support Angular i18n (partially)
1 participant