-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Initialize/activate the ExtensionLocators
when the extension activates.
#13498
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
Initialize/activate the ExtensionLocators
when the extension activates.
#13498
Conversation
Codecov Report
@@ Coverage Diff @@
## main #13498 +/- ##
==========================================
+ Coverage 59.91% 59.96% +0.04%
==========================================
Files 682 684 +2
Lines 37935 38029 +94
Branches 5462 5477 +15
==========================================
+ Hits 22730 22804 +74
+ Misses 14046 14043 -3
- Partials 1159 1182 +23
Continue to review full report at Codecov.
|
5c3a84d
to
04cb74e
Compare
636b062
to
41f0f4b
Compare
ExtensionLocators
when the extension activates.
If you don't mind moving those, that would be super helpful. Thanks! |
Sorry for making this PR complicated by the other one. I got impatient. 😄 |
41f0f4b
to
b4afa82
Compare
b4afa82
to
820df93
Compare
SonarCloud Quality Gate failed.
|
This finishes up work on "interfaces and scaffolding needed for locators". At this point we can plug this "locator manager" into the discovery component API, as well as plug the low-level locators in here.
[ ] Has a news entry file (remember to thank yourself!).[ ] Has sufficient logging.[ ] Has telemetry for enhancements.[ ] Unit tests & system/integration tests are added/updated.[ ] Test plan is updated as appropriate.[ ]package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed).[ ] The wiki is updated with any design decisions/details.