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
{{ message }}
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
I wrote a detailed question on stackoverflow if anyone could answer, but I'll ask the concise version here:
I would love to leverage something like jsonform so that my UI team could generate a UI form based off the json-schema I provide them. This would cut down tremendously on the hours spent in meetings describing business requirements or how the UI needs to flow. However, this appears to me to tightly couples the backend to the UI. Is there any drawback to this approach or concerns I should look out for?
Best regards!
(I am cross posting this in the 3 jsonform's I see on github for some more visibility)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I wrote a detailed question on stackoverflow if anyone could answer, but I'll ask the concise version here:
I would love to leverage something like jsonform so that my UI team could generate a UI form based off the json-schema I provide them. This would cut down tremendously on the hours spent in meetings describing business requirements or how the UI needs to flow. However, this appears to me to tightly couples the backend to the UI. Is there any drawback to this approach or concerns I should look out for?
Best regards!
(I am cross posting this in the 3 jsonform's I see on github for some more visibility)
The text was updated successfully, but these errors were encountered: