-
Notifications
You must be signed in to change notification settings - Fork 2
Add const file for string #11
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
Comments
If these are user facing strings then I think we should go with some type of internationalization. https://hexdocs.pm/gettext/Gettext.html Seems to be what Phoenix includes by default. More info: https://medium.com/@erichkist/using-gettext-to-internationalize-a-phoenix-application-ceb410407ea5 |
@codeithuman Jumping on to what @ryanlntn said, I think I18n is the route we should go. linguist is also an option if we want something a bit simpler than gettext. |
Totally down with linguist too. I'd prefer to work in plain elixir code. There are some advantages to Gettext though like the |
Yeah, linguist is more of a key-value store than a full-on I18n solution. |
How should we manage strings within our phoenix applications? Flash messages, error messages, validation messages, etc.
The text was updated successfully, but these errors were encountered: