You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you think about updating WebUI? My suggestion is to use the JS framework for the frontend. For example, Vue.
Benefits:
can be made one-page application
on the main page you can display more information. For example, the number of untranslated messages, the total translation percentage, domains, etc.
on the locale page, you can visually display which translations are translated, which are not, and which ones are custom.
search and filtering translations
optional - display only non-translated messages (that would be the case for large message domains)
Possible disadvantages:
use API endpoint for receiving MessageCatalogues. But since catalogues must be loaded once and not needs large performance it can be not disadvantage, rather another ability - for example behavior like in this bundle. Need your thoughts.
better will be use npm (end user must build js assets also), but Vue app also can be created without building.
--
Some time ago I created a plugin to manage translations in Sylius. It was rather a desire to practice writing plugins, rather than replacing existing solutions. And, having written to Slack, I received advice to try to add some features to the existing bundles (this one was indicated). And I would be glad to participate. However, I cannot be sure that the approach used in my plugin will fall on the architecture of this bundle. You can check my service and controller.
Perhaps, before trying to do something like prototype - it is worth checking with the maintainers whether it will be necessary and useful at all.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
What do you think about updating WebUI? My suggestion is to use the JS framework for the frontend. For example, Vue.
Benefits:
Possible disadvantages:
--
Some time ago I created a plugin to manage translations in Sylius. It was rather a desire to practice writing plugins, rather than replacing existing solutions. And, having written to Slack, I received advice to try to add some features to the existing bundles (this one was indicated). And I would be glad to participate. However, I cannot be sure that the approach used in my plugin will fall on the architecture of this bundle. You can check my service and controller.
Perhaps, before trying to do something like prototype - it is worth checking with the maintainers whether it will be necessary and useful at all.
Thanks.
The text was updated successfully, but these errors were encountered: