-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add aah generate i18n
command to generate i18n vars
#119
Comments
Wait, this would potentially scan through the entire codebase to determine the |
@adelowo Thanks for asking. This is an idea. As you know localizing application is considerable effort, aah CLI is gonna help on that. So command creates i18n placeholder then aah user fills in the locale based values in it. Let's move on to implementation part:
Steps:
Sample
Please let me know your thoughts. |
Understood.... I am just more worried about updates. Does this plan to support update operations like running the command again after making some changes to the views - even though it was previously generated ? |
@adelowo That's a good question and concern. Yes, user can run BTW, Currently Would you like to try on it?
|
I would take a stab at it next week if it has not been worked on |
@adelowo I'm glad to hear that, No I'm not working on it. I have shared my idea with you today. Currently I'm doing my homework on Websocket and Configurable roles/permissions for each route definition. |
This depends on #231 |
Hello,
Besides
aah generate
which could be used for whole generation about MVC (model needs database layer) I would like to present a functionality that I thought about i18n. The idea is to be able to generate amessages
file like below in this example:For i18n, if I have
i18n . "page.site.title.index"
in a view (so that's for eachi18n
vars defined in view) , I will write in CLIaah generate i18n fr
, then it will generate amessages.fr
file with:We already talked about that @jeevatkm in gitter, that's why it's already in roadmap. This issue is intended to precise it :).
Thank you very much! :D
The text was updated successfully, but these errors were encountered: