I really like your work on this. The only things I would probably change, would be to make button interactions "do" more on-click. Also, I'd probably have the text/textarea etc have an "invalid-color" attribute that applies to the text/border when the component is invalid, or have some other target beyond wrapping the entire component itself.
I also tend to activate validation as part of onBlur and keep it through all change events from then onward, red while invalid to green when corrected. Haven't really played with the library much just looked through the components themselves. I just tend to pay extra attention to the form fields, date pickers and a few other areas that a lot of component libraries tend to miss.
Definitely appreciate all your work on this and it's very cool indeed... may play with it for a small yew project I've been thinking of.
Not really a good current example. In the past I've done the redux integration with react-router and a few other bits... that got "interesting" to say the least. So I know enough to know it's a pain to hard wire all of it up and get it working to trigger from/to the browser, redux, etc and having things sync right.
If I were building from scratch today, I'm somewhat inclined to look at tanstack router, not that I'd use all of tanstack. React-Router itself has just been kind of a mess along the way. It's been a couple years since I've been able to start a UI project from scratch instead of inheriting what's already in progress though.
Not sure I appreciate the title... I had a bit of a visceral reaction to the title because I had expected an advocation for a brute force method over the (Map|Object).groupBy static methods that are mentioned.
As opposed to something like: "For Array to Object Mapping, Use groupBy Not reduce"
Kind of cool to see this... Definitely useful for something like an editor/forms environment for near state. Probably a bit harder to integrate with something like page navigation actions, especially with route changes... though can probably track/attach the state/step with route changes for better undo/back and forward tracking.
Yeah... I'd like to get them on the submission page as well... also likely with a captcha as part of submissions to slow/stop the bots.
I don't generally have time to mess with the app codebase here, mostly just act as a moderator.
Yeah... I don't see an exception in the LICENSE.txt but it's mentioned in the README. Looks like they want to restrict commercial apps to only the commercial licensing.
Per the posting rules in the about page... No commercial content or libraries (even with free demo)See about page: - No commercial content or libraries (even with free demo)