Skip to content

fix: use current event modifiers syntax in render function #302

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

Closed

Conversation

damianstasik
Copy link
Contributor

To make .passive, .capture and .once event modifiers JSX-friendly, the syntax was recently changed to allow passing them in the camelCase notation right after the event name. I added the note about combining them and extended the example to include the .passive event modifier just in case.

@skirtles-code
Copy link
Contributor

@visualfanatic It looks like the changes you were proposing are quite similar to #552, which has now been merged.

Given the current conflicts, I think it would be best to close this PR. Do you agree?

I can't speak for anyone else but I think it would be remiss of me to suggest closing this PR without also acknowledging the long delay in giving you any feedback. I dare say that's quite frustrating for you. I don't know why that happened but my guess would be that there was a good reason why it couldn't be merged immediately and then it got forgotten about. My own feeling is that this is more likely to happen when there are a lot of open PRs, so I'm trying to help out by reviewing all the old PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants