Simon André
Simon André
[LiveComponent] `data-model` started throwing the "Invalid model name" error after upgrading to 2.15
> This part is a bit confusing since when you install symfony --webapp it comes but then needs to be removed for the ux-live installation. This can be confusing i...
[LiveComponent] `data-model` started throwing the "Invalid model name" error after upgrading to 2.15
The documentation is really big today, so it's not always easy to emphasis things or illustrate. We are thinking about splitting it in multiple pages (per "feature") and @WebMamba started...
Let's keep the "required" and there is no problem.. you should not be able to submit without selecting a value. (try without `novalidate: true,` )
This is the only "solution" i have .... as I don't see any bug on the demo. Please look at the following video. https://github.com/user-attachments/assets/3d368883-ac59-476b-93f2-3aa8b6fdc909
-- friendly tone here 😃 -- i just spent 15 minutes to understand your problem, replicate it, point were you missed something, record and post a video to show you...
> My tone was meant to be "normal" I know ;)
For the record: the discussion continued acrosss repositories (😅 ) but point is: there _**is**_ some case not fully covered / implemented in the DependentFormField here... Let's see if we...
Let's imagine all is easy and possible. So regarding the best user-experience in this scenario.. .... what would be the best behaviour for a user, just after selecting "Office 3"...
> But look what happens when [...] I do agree this is a weird situation, and we'll try to find a good solution, but you cannot compare to anything "not...
> But in this case, the form updates as soon as you select 'office 3,' and then everything gets stuck I know i know ... 😅 > Option 1, set...