alexciesielski
commented
7 months ago I played around with it a bit and also read up on shadcn and figured it out. It seems the idea behind shadcn (and therefore behind spartan) is to have full control over your component library, meaning you own your code, but that also comes with the downside of having to manually change it whenever updates to shadcn/spartan appear.
I'll get to coding then :) let me know if there's anything I can contribute and maybe also where to find a list of tasks.
Hey, first of all - amazing work. I definitely plan on becoming a contributor (sidenote: I would love to see a list of issues that would suggest what I could start contributing to).
I just used the nx plugin to scaffold the code for the input and button to get a feel for the library, and immediately I started wondering how I should use/extend the button for example.
Let's assume I want to add a [loading] input to all my buttons. If I add it directly to the generated helm button, I assume I will run into problems in future versions if I rerun the generator?
Or will there be nx migration scripts?
Or in other words, can you elaborate how the upgrade process will look like?