[breaking changes] Pending changes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary
Over the years, I have seen too many cases where we think about breaking changes that we could make that would help, but we forget to do them, we are left with TODO in the codebase. So this issue is meant to list them all, so we can be effective in how we manage breaking changes.
In theory, each item could have a dedicated GitHub issue:
The important part is that it's not because a breaking change is better for new users, that we should do it, because it can degrade the UX of existing users, too much. So they are more ideas than anything else:
- Set
resetHighlightOnMouseLeaveby default #48354.
Examples
No response
Motivation
No response
Search keywords: -
Contributor guide
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
Start by reviewing the checklist in issue #48547 and the linked resetHighlightOnMouseLeave item, #48354. This issue has no specific files, tests, or acceptance criteria; work is only defined once an individual breaking-change idea is split into a dedicated issue with a clear scope and completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100