- Notifications
You must be signed in to change notification settings - Fork 1.3k
Clean up the extension activation code. #10455
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
Clean up the extension activation code. #10455
Conversation
08516fd to 5b3d57d Compare Codecov Report
@@ Coverage Diff @@ ## master #10455 +/- ## ========================================== - Coverage 60.86% 60.81% -0.05% ========================================== Files 579 578 -1 Lines 31290 31276 -14 Branches 4449 4448 -1 ========================================== - Hits 19045 19022 -23 - Misses 11282 11289 +7 - Partials 963 965 +2
Continue to review full report at Codecov.
|
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.
Looks alright, mostly moving things around :)
Could you rename the extension-* files you created to use the camelCase file naming convention we have in the codebase instead of kebab-case?
| Kudos, SonarCloud Quality Gate passed!
|
* master: Fix flakey file system tests (#10541) Tweaks for gather (#10532) Fix #10437: Update launch.json handling to support "listen" and "connect" (#10517) Add conda support to nightly flake test (#10523) Rename datascience to datascience_modules (#10525) Clean up the extension activation code. (#10455) Allow escape and ctrl+U to clear the interactive window (#10513) Fix builtins so they don't interfere with our execution (#10511) Jupyter autocompletion will only show up on empty lines, (#10420) notify on missing kernel and interpreter with kernel (#10508)
(for #10454)
This is the basic prep work for making the flow of extension activation more clear.
[ ] Has telemetry for enhancements.[ ] Unit tests & system/integration tests are added/updated.[ ] Test plan is updated as appropriate.[ ]package-lock.jsonhas been regenerated by runningnpm install(if dependencies have changed).[ ] The wiki is updated with any design decisions/details.