Skip to content

[docs] Document the effect of the order of bind: and on: #6887

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

Merged
merged 2 commits into from
Nov 8, 2021

Conversation

gtm-nayan
Copy link
Contributor

Closes #6197

After reading the maitainers' views on #5166, I think a simple note like this would be sufficient.

on: and bind: have separate sections for components and elements but from a beginner's perspective this seems like the most natural place to have it.

I'm not sure what, if anything would need to be added in any of the tutorials, I'd appreciate some comments on that.

Before submitting the PR, please make sure you do the following

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • Prefix your PR title with [feat], [fix], [chore], or [docs].
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with npm test and lint the project with npm run lint

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

Successfully merging this pull request may close these issues.

Order of bind:value and on:input in component property list affects value in input event listener.
4 participants