-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
[breaking changes] Pending changes #48547
Copy link
Copy link
Open
Labels
breaking changeIntroduces changes that are not backward compatible.Introduces changes that are not backward compatible.scope: all componentsWidespread work has an impact on almost all components.Widespread work has an impact on almost all components.
Description
Metadata
Metadata
Assignees
Labels
breaking changeIntroduces changes that are not backward compatible.Introduces changes that are not backward compatible.scope: all componentsWidespread work has an impact on almost all components.Widespread work has an impact on almost all components.
Fields
Give feedbackNo fields configured for issues without a type.
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:
resetHighlightOnMouseLeaveby default [autocomplete] Enable clearing highlight when mouse leaves popup #48354.Examples
No response
Motivation
No response
Search keywords: -