We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think i create around 50 TwigComponent for 1 LiveComponent ...but my personal experience may not be enough to claim any general case 😅
During the interaction, the "Make this a live component" defaults to yes.
yes
Same thing if an arg is given:
sf make:twig-component FooBaz Make this a live component? (yes/no) [yes]: > n
What do you guys think ?
The text was updated successfully, but these errors were encountered:
deferring to @weaverryan as ux is more in his wheelhouse
ux
Sorry, something went wrong.
Agree - defaulting to NOT live makes sense.
[make:twig-component] default to "no" when asking if is live component
56fb4d9
fixes symfony#1395
32cbea5
Successfully merging a pull request may close this issue.
POV
I think i create around 50 TwigComponent for 1 LiveComponent
...but my personal experience may not be enough to claim any general case 😅
Current behaviour
During the interaction, the "Make this a live component" defaults to
yes
.Same thing if an arg is given:
Suggestion
What do you guys think ?
The text was updated successfully, but these errors were encountered: