-
Notifications
You must be signed in to change notification settings - Fork 457
Make sure deprecated is always a string #2271
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
github-actions
merged 9 commits into
microsoft:main
from
Bashamega:deprecated-string-only
Dec 7, 2025
+48
−45
Merged
Changes from 4 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
455185e
Update deprecation messages in generated TypeScript definitions and K…
Bashamega 3b3f60c
Update webkitLineClamp support status in KDL and adjust TypeScript ha…
Bashamega 6d142a0
lint
Bashamega 359d50d
Merge branch 'microsoft:main' into deprecated-string-only
Bashamega c02102f
Update KDL to deprecate webkitLineClamp in CSSStyleProperties and enh…
Bashamega 37b41cb
no `supported` anymore
saschanaz f3ec07b
random property values are all for removals
saschanaz bd3d1e7
optionalNestedMember
saschanaz 1075f7b
amend deprecation messages
saschanaz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,4 @@ | ||
| dictionary KeyboardEventInit { | ||
| // TODO: pass a string instead for deprecated | ||
| // charCode is inconsistent across environments, consider using .key instead | ||
| member charCode deprecated=#true | ||
| // keyCode is inconsistent across environments, consider using .key instead | ||
| member keyCode deprecated=#true | ||
| member charCode deprecated="CharCode is inconsistent across environments, consider using .key instead" | ||
| member keyCode deprecated="KeyCode is inconsistent across environments, consider using .key instead" | ||
| } |
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A better way would be to remove the field through
removals, although it's not supported yet. Maybe that should be the first step.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you share the syntax for it @saschanaz I can't imagine it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something like
Or perhaps it's easier to keep using each property's own type, like
deprecated=""and let it converted to null via the removal conversion function. Either way would be fine for me.