-
-
Notifications
You must be signed in to change notification settings - Fork 364
Stimulus controllers: allow to define outlets #942
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
Conversation
I've just seen that the PR on Webpack Encore bundle adds an Also, should I PR against Encore bundle (v1) if this PR gets merged? |
Hello | ||
</div> | ||
|
||
<!-- would render --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-would+will ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just followed the other examples (that I didn't write); should I change them all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont know :/
I was just reviewing unitary lol
Thanks @jmsche! This looks great |
@weaverryan Should I also PR against Encore bundle (v1)? |
@jmsche I don't think so. My thinking is that upgrading from EncoreBundle 1 to 2 is trivial. And 1 should be considered in maintenance - bug fixes only. |
I guess symfony/webpack-encore-bundle#205 & symfony/webpack-encore-bundle#206 can be closed then? |
This PR allows to define outlets to Stimulus controllers. See https://stimulus.hotwired.dev/reference/outlets
Also updated .gitignore as running PHPUnit locally generated a
.phpunit.result.cache
file.