Fix version in useSetting deprecation notice #56377
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fabiankaegy
added
the
[Type] Developer Documentation
youknowriad
approved these changes
Nov 21, 2023
|
Size Change: +46 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
|
This also needs an unit test update because the warning string is checked in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Fix the Version number used in the deprecation notice of the useSetting hook
Why?
Because it didn't ship in time for 6.4 and therefore isn't actually deprecated in 6.4
How?
Update any reference to 6.4 with 6.5
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast