Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Split fluent and gettext systems in i18n-embed out into sub-crates #103

Open
kellpossible opened this issue Feb 27, 2023 · 1 comment
Open

Split fluent and gettext systems in i18n-embed out into sub-crates #103

kellpossible opened this issue Feb 27, 2023 · 1 comment
Labels
good first issue Good for newcomers refactor Improving the maintainability of the code

Comments

@kellpossible
Copy link
Owner

The systems in i18n-embed are never going to be used together in a project, so it makes sense to put them in sub-crates.
@kellpossible kellpossible added refactor Improving the maintainability of the code good first issue Good for newcomers labels Feb 27, 2023
@kellpossible
Copy link
Owner Author

It would also be kind of strange to have other systems appear in your autocompletion some libraries may use another system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers refactor Improving the maintainability of the code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kellpossible