`v-on` modifier `.once` triggers handler at most once... per what?
Open
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 3.2k
- Forks
- 5k
- Avg merge
- 14d 17h
- Merged PRs (30d)
- 1
Description
I found the statement above unclear, because this could imply the listener would be called once per:
- an event,
- a mount,
- an update or
- a span in lifecycle (possibly specified somewhere).
This could lead readers to assume the semantics or simply avoid using this modifier not to cause confusion.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open src/api/built-in-directives.md at the linked v-on modifier section and review the wording around .once. Clarify the scope of “at most once” so readers can tell when the handler may run, then verify that the revised statement resolves the listed interpretations.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100