-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users are expecting more than layout from vaadin-form-layout
#28
Comments
This is the situation for 1.0, and it is reflected in the name, right? Also, there have been vague plans about adding more form features to it in the future, like you mentioned, or generating a form out of a JS object automatically. |
Rigth.
In that case, the |
Yeah, probably. But those plans are really vague at the moment, so I wouldn’t worry about it. We can introduce another element for those features if needed, and use this layout inside it. |
Add a notification that it's only about the layout, nothing more than that. |
The description at https://vaadin.com/components/vaadin-form-layout is probably enough.
Also the component is under "Layouts" block at https://vaadin.com/components. So I'm closing this issue as outdated. The need for a form component can be discussed in other issues, and we have a place for it at https://github.com/vaadin/proposal-for-vaadin-form. |
Probably we should consider renaming the element or adding a well visible statement in docs that
vaadin-form-layout
is only about the layout, there's nothing about validation or object with fields' values, etc.(This is the DX tests finding)
The text was updated successfully, but these errors were encountered: