Almost done with a basic setup (including types), for a bunch of renderers build on top of forms that adhere to the json schema specifications, and uses #jsonforms to render it all.

With our product supporting just any combination of form elements (shipping / logistics forms) it's a challenge to create something that works over multiple services, is easy to create on side and eventually easily renderered on the other.
Writing renderers for use with jsonforms is trickier than it seems. But when you deal with a lot of complex forms (that are generated in different service) than using #jsonforms jsonforms.io is a good tool to use. Built in validation, adhering to the json schema json-schema.org and integration with different frameworks.

Now could it be a little less verbose, so it handled a bit easier? yes
Could they maybe rename tester to something different, so renderer weight determination is not as tucked away? also yes

There is a bunch of things that are hard about it and feel sometimes to be backwards, but when you have something working, it is super nice!

Expecting to put a lot more time and effort into it in the future. (not today, now it's time for the weekend).
More forms. Less code. - JSON Forms

More forms. Less code.

One advantage, other than dead simple validation controls, of switching from #jsonforms to #formik means I have far more control of how the UI works.

#React #ReactJS #forms

What a day… Ended yesterday off with trying to get form level validation working with #jsonforms, this morning I decided it’s a better use of my time to just move over to #formik instead. Took less time to rewrite than it had taken to get half the validations working, and that was a hack at best.

#forms #React #ReactJS

Siedzę tak sobie nad #JSONForms i żałuję, że jestem taki cienki... Próbuję połączyć to z #A11YJSON i wciąż wychodzi mi, że jestem na to za głupi. Żeby się nie przygnębiać - zajrzę do innych rzeczy.