Introduce preset componentsSee original GitHub issue
This is an idea and proposal to simplify the usage of several things.
Building a view using UI components is great, it makes it easy and fun. However there is one little issue that is kind of annoying and that you end up doing all over again: duplicated messages.
For example, when you build a form you usually need a
Save button. So you usually end up creating messages for those buttons because the UI components require you to pass a label.
This happens for other things that are spread all over the different views.
And of course you end up having A LOT of duplicated messages to be translated, when 99% of the cases might not be necessary.
It would nice to have some sort of “preset” components that are translated and everything within the ui-kit, so that as a consumer we don’t need to care about all those messages again.
…and whatever other components might be useful.
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top GitHub Comments
Can’t app-kit expose those?
and we do:
Yes, that’s what I meant with the “preset” thingy. It’s just a grouping for such components.
I know, I couldn’t find a better name to describe this 😅