We have plans for more goodies to add and we’d love to see contributions from anyone else. (Get a PR accepted and you become a band member complete with the lovely logo added to your github profile)!
Quick Start
Clone the app, add it as a dependency and play around:
Wait a second… is this it? Is my music degree about to pay off?? Can it finally be happening after all these years??? I thought this day would never come… (Abandon all hope, ye who pursue music degrees.)
When choosing his major, 18-year-old Kevin had not yet learned to code, but at least I got a few guitars out of the deal. As well as enough regret to become a decent Blues player.
But… What are your thoughts about splitting all the tools into single dependency apps?
I used to have one app called Common Components and I used to use it as a dependency for all my new apps.
At a certain point I had a long list of custom components on the toolbox that was ugly and forced me to scroll down to see the selected component properties.
Then I learned that all my apps were slow because they kept importing tons of useless stuff.
And all the apps depended on tables that they didn’t really need. For example some apps don’t require authentication or user management, but I had to set them up with the user service and the user table. And some apps didn’t need certain parameters, but I had to set them up with a global parameter table.
So I dismembered that Common Components app in many little apps, each with just one or a few custom components or with just one server module, and everything seems to be running smoother.
Well, nothing in there requires a data table and each element can be imported in isolation, so it should be OK. Just don’t import the whole thing anywhere!