@flyboarder hmm this is where it gets difficult, data validation is a really deep topic
we've moved past tracking async processes into something a lot more complicated
however we dont need to be responsible for the validation, only the result of validation
the thing about my implementation, is that any bit of implicit state can be explicitly set, so if a component wants to manage any of it itself it still can
*status* is where I would put this type of state
I just updated the snippet above to include
*success*, also this will be part of the repo here eventually: https://github.com/degree9/enterprise
kk, i'll think about it a bit more and offer some feedback 🙂
hello again, guys!
i might have a chance to get back to hoplon on a project.
i just ran thru the changelog; tons of things have changed... @flyboarder @thedavidmeister i see 7.x was mostly the result of your commits. Q1. what's the best example repo currently which demonstrates the capabilities of Hoplon 7.x? Q2. is there a widget library you can recommend? Q3. https://github.com/hoplon/demos doesn't seem to be updated; why is that?
boot-reload be linked to https://github.com/adzerk-oss/boot-reload at https://github.com/hoplon/hoplon/blame/master/README.md#L68 for example?
@onetom I don’t think there are public example projects yet which use the new
7.X versions, however they should be Fully compatible with the last
6.0-alpha series, most of the changes are internal not public facing