Which scope/s are relevant/related to the feature request?
Don't know / other
Information
I think there is a lot of merit in also copying the brain components, like the helm components into the devs workspaces in order to tweak the components as a whole. Changing the complete look and feel of any component via the helm directive is a great thing.
However many times in my relatively short career I have found the need to change the deep inner logic of a component in order to have my customers or my own functionality needs met. Many UI Libraries lack special case functionalities in their tables and other more complex components. This is, for many developers, a complete disqualifier for those libraries, not just the one component.
I realize adding features on top is easily possible by just wrapping third party components such as spartan, however changing the inner workings and slightly changing existing functionality is not possible in this way.
Giving every single developer the opportunity to tweak spartan component functionality or add a new functionality according to their own special needs would be such a big win, catapulting spartan to the top of angular ui libraries.
Implementing this should be trivial with hlm files being copied over already. The only drawbacks I can think of are bundle size. This could be limited by making this functionality optional via a parameter in the scripts.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
Which scope/s are relevant/related to the feature request?
Don't know / other
Information
I think there is a lot of merit in also copying the brain components, like the helm components into the devs workspaces in order to tweak the components as a whole. Changing the complete look and feel of any component via the helm directive is a great thing.
However many times in my relatively short career I have found the need to change the deep inner logic of a component in order to have my customers or my own functionality needs met. Many UI Libraries lack special case functionalities in their tables and other more complex components. This is, for many developers, a complete disqualifier for those libraries, not just the one component.
I realize adding features on top is easily possible by just wrapping third party components such as spartan, however changing the inner workings and slightly changing existing functionality is not possible in this way.
Giving every single developer the opportunity to tweak spartan component functionality or add a new functionality according to their own special needs would be such a big win, catapulting spartan to the top of angular ui libraries.
Implementing this should be trivial with hlm files being copied over already. The only drawbacks I can think of are bundle size. This could be limited by making this functionality optional via a parameter in the scripts.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue