-
Notifications
You must be signed in to change notification settings - Fork 540
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
Run lint:fix on Container Runtime to remove suprious deprecations #24022
Conversation
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.
PR Overview
This PR applies a lint fix to remove several spurious deprecation comments throughout the Container Runtime code. The key changes include the removal of redundant “eslint-disable-next-line import/no-deprecated” comments from various files and adjustments to the surrounding whitespace.
Reviewed Changes
File | Description |
---|---|
packages/runtime/container-runtime/src/gc/gcConfigs.ts | Removed redundant deprecation directives from import statements. |
packages/runtime/container-runtime/src/summary/summaryFormat.ts | Cleaned up deprecation comments alongside metadata-related exports. |
packages/runtime/container-runtime/src/containerRuntime.ts | Removed several deprecation comments from core runtime code, with minor whitespace changes. |
Copilot reviewed 18 out of 18 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (3)
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.
Too bad lint:fix leaves a bunch of blank lines in funny places and nothing will fix 'em up.
Wonder if the better process is to remove all of them from a package and then let lint:fix restore the one that are needed.
// eslint-disable-next-line import/no-deprecated | ||
|
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.
Would be nice if most or all of these were just deletions
// eslint-disable-next-line import/no-deprecated | ||
|
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.
This gap is definitely funny.
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.
yeah. its just want es-lint auto fix does. i don't really like it, but i also not keen on doing a bunch of manual clean up
it looks like es-lint doesn't know how to add inline suppressions, or i don't know how to do it, so it would again require a bunch of manual fix ups. |
Yeah - I don't know how to apply disables other than IDE option. Makes some sense because it can't be "fixed". Maybe the more recent versions of linter do a better job. I am guessing these no longer need to be legacy+alpha: At least I don't see hits for them in any other *.api.md files. |
…crosoft#24022) Just ran link fix to remove any spurious deprecation lines, including those created by microsoft#23981
Just ran link fix to remove any spurious deprecation lines, including those created by #23981