chore(config): add @deprecated tags to plugin hook utilities - #23250
Open
syedsohailhussain1 wants to merge 2 commits into
Open
chore(config): add @deprecated tags to plugin hook utilities#23250syedsohailhussain1 wants to merge 2 commits into
syedsohailhussain1 wants to merge 2 commits into
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 is this PR solving?
This PR fulfills an outstanding
TODOinconfig.tsby adding@deprecatedJSDoc annotations togetSortedPluginsandgetSortedPluginHookson thePluginHookUtilsinterface (which is exposed viaResolvedConfig). This ensures that downstream plugin authors receive proper IDE warnings, pointing them toward the newerconfig.environmentsAPI.Reference the issues it solves
N/A (resolves an internal codebase TODO)
What other alternatives have you explored?
N/A - this is a direct implementation of a planned deprecation comment left by the core team.
Are there any parts you think require more attention from reviewers?
No, this is a straightforward types-only change that doesn't alter any runtime behavior.
Tests
Tests are not included because this is strictly a TypeScript JSDoc annotation update and does not change any runtime logic.