You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, do you think maybe we should consider this a sign to "unpromote" this
feature for the 1.0 release, making it an undocumented private api that can
be deprecated in the future?
This way, if there really is not much use for it, we can make uniforms even
leaner, concentrating our efforts on what matters the most.
And imho, anyone dealing with forms would either eventually want to fine
tune what's enclosed within the autoform tags or at least not be bothered
by the fact that defining a form requires defining its fields within the
jsx markup, since you know, it is what everyone is already used to doing
anyway. In fact, perhaps full autoform is an unexpected feature for most
people and they might even find it unreliable, and be better of defining
explicit markup!
To be honest - no. I've also encountered this before, but since then I always provided an initial model.
I thought about it at the beginning, but there are some cases when it's a lot simpler. For example - your schema is generated (by a GUI editor or from simple textual definition) - then you have either to use fullAutoForm or to extend your GUI editor to handle it.
I don't think, that any feature right now should be unpromoted (or treated as legacy) - those are obvious to come.
Using schema:
I've created full form by
AutoForm
:I haven't checked a checkbox, after submit I've got
{boolValue: ''}
(empty string).The text was updated successfully, but these errors were encountered: