The short answer is no. If it’s working and you feel good about it not breaking, go ahead.
The way these frameworks keep changing and breaking just cross your fingers you will have not to revisit code.
Unfortunately in my camp it’s been mostly trial and error getting something to work and stable.
I find it very funny and sad that I hit on these posts in my searches. Worst of all, is when I hit on my own posts two years later.
I have lost trusts in most frameworks WindowsSDK, ATL, Silverlight, WPF, AndroidSDK, ionic, angular, because they fail while working with the basic concepts. Every component will surprise you sooner than later with a weird behavior or limitation. Why should an ion-toggle or ion-range deserve so many posts? A stop at the docs should be sufficient.
I hate semicolons in C (during college compiler courses),
I hate semicolons in C# and every other language.
While I am editing, I take special joy deleting semicolons in my ionic apps
If the compiler wants semicolons let it shove them where it wants to.
I hate stupid case sensitive languages and OS (security? yeah, right!)
Linux will eventually succumb, it started supporting case-INSenSitive filesystem, just last year.
English has only 26 characters let’s not invent more, “B” and “b” are just glyphs not separate characters.
Don’t feel you have to use any particular Casing Conventions, it’s only meant for those control freak in your enterprise team.
The most stupid of all is cAmElCaSe
Case conventions should be something I configure in my editor don’t try to force it on me.
When something is case sensitive I purposely use ALLCAPS just to see if I can blow some of its bolts off.