-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Infolist form component #11753
Comments
This will solve some hacks in my code base |
would be cool to use infolists components on forms too 😅 |
That's exactly what this issue is about :) |
@zepfietje Oh, i thought it was the opposite. Then it would be cool to use Forms components on Infolists 😅, for quick editing like a title or smth. I'm currently using a |
That would really still be a number of infolist entries in a form with a single field then, right? |
yes if you're not using an infolist on the view page, only a disabled form. if you wish to use both, a form for creation/editing process and a infolist to display data while allowing some field to be quickly edited on the view page, we need to support form components inside infolists. |
Actually a cool way to do that would be simply have a infolist view option for a every form field. This way you could display a form in a read only mode that would simply look like an infolist. No need to manage two versions of it. |
That way we can't have separated layouts for the form/ infolist. Take a blog post for example, the form layout for creating a blog post is very different than the infolist for viewing a post. |
Hello I'm searching for this. Does this got committed somewhere or just closed as not planned? 😅 |
Closed as completed in v4 |
still possible if you use a nested LW component in v3 |
No description provided.
The text was updated successfully, but these errors were encountered: