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
The issue is that, just like a function you extract off an object, once the field is individually rendered, it doesn't have the context to know it's supposed to be nested inside filter.
I could imagine some kind of API on the form object to directly render a specific field's HTML, but it'd require some kind of magic to allow for field → uname, for example, to be represented.
Given the following form definition:
On the template side, if I draw the form using
!=formFilter.toHTML(bootstrapField)
I get the following query:
But if I draw the form fields individually (because of layout needs):
I get:
I would expect the input names to be derived from the form structure, regardless of how they are rendered. Is there any workaround? Thanks!
The text was updated successfully, but these errors were encountered: