Skip to content
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

Closed
danharrin opened this issue Mar 7, 2024 · 11 comments
Closed

Infolist form component #11753

danharrin opened this issue Mar 7, 2024 · 11 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@danharrin
Copy link
Member

No description provided.

@danharrin danharrin added the enhancement New feature or request label Mar 7, 2024
@danharrin danharrin added this to the v3 milestone Mar 7, 2024
@danharrin danharrin self-assigned this Mar 11, 2024
@hussain4real
Copy link
Contributor

This will solve some hacks in my code base

@saade
Copy link
Member

saade commented Mar 12, 2024

would be cool to use infolists components on forms too 😅

@zepfietje
Copy link
Member

would be cool to use infolists components on forms too 😅

That's exactly what this issue is about :)

@saade
Copy link
Member

saade commented Mar 13, 2024

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 Infolists\Components\Livewire::make(MyCustomForm::class)

@zepfietje
Copy link
Member

That would really still be a number of infolist entries in a form with a single field then, right?

@saade
Copy link
Member

saade commented Mar 14, 2024

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.

@MACscr
Copy link
Contributor

MACscr commented Mar 14, 2024

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.

@saade
Copy link
Member

saade commented Mar 14, 2024

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.

@dangnhdev
Copy link

Hello I'm searching for this. Does this got committed somewhere or just closed as not planned? 😅

@danharrin
Copy link
Member Author

Closed as completed in v4

@danharrin
Copy link
Member Author

still possible if you use a nested LW component in v3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

6 participants