Draft Disclaimer: Please note that this article is currently in draft form and may undergo revisions before final publication. The content, including information, opinions, and recommendations, is subject to change and may not represent the final version. We appreciate your understanding and patience as we work to refine and improve the quality of this article. Your feedback is valuable in shaping the final release.
Language Mismatch Disclaimer: Please be aware that the language of this article may not match the language settings of your browser or device.
Do you want to read articles in English instead ?
Does livewire send too much requests
When and when not to use it
Some of these concerned solve in livewire 3.x
Pros
Cons
Not suitable for nested dynamic components example delivery form
- 2 address picker (for pick up and delivery)
- 2 user autocomplete (for pick up and delivery when user is staff/admin)
- communication between Form component and other 4 components
- sending request to update for all instances of livewire component on update via emitted event.
- prefilling on delivery.edit is sending 4 request (yes just to prefill)
- that wouldn't be suitable for scaling
Workaround
- have selected/filled state address.picker or markup for selected/filled state