Fix form properties fill from URL #9318
Conversation
|
Hello @calebporzio, could you take a look? |
|
Would recommend not using fill in this approach. Generically, to my mind, your Form is your reusable create/update interface. It is how you map your frontend forms, against your component/backend logic. Developers should map querystring against a form object themselves via the Component, rather than the Form. Keeping querystring logic in the Component keeps it consistent, and simple. Otherwise this is potentially a slippery slope, if Component level features start being added to the Form, then it defeats the purpose of the Form being a lightweight way to reuse frontend/backend interfaces. |
Review the contribution guide first at: https://livewire.laravel.com/docs/contribution-guide
1️⃣ Is this something that is wanted/needed? Did you create a discussion about it first?
2️⃣ Did you create a branch for your fix/feature? (Main branch PR's will be closed)
3️⃣ Does it contain multiple, unrelated changes? Please separate the PRs out.
4️⃣ Does it include tests? (Required)
5️⃣ Please include a thorough description (including small code snippets if possible) of the improvement and reasons why it's useful.
Thanks for contributing! 🙌