Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Stop MEF exporting FilePathService from the Workspaces layer #10118

Merged
merged 20 commits into from
Mar 20, 2024

Conversation

davidwengier
Copy link
Member

One of the items in #10103

Part of #9519

One of the items in #10103

Part of #9519

Rather than move telemetry down into the service, I decided to leave it
in the endpoint, and C# specific service, so we can track separate
telemetry from existing LSP, to make it easier to report on. In theory
this is unnecessary because we already would know the status of A/B
flights in the telemetry data, but that doesn't allow for manually
switching the flag. If people feel strongly about not using different
properties, I'm fine to change. Perhaps all of our telemetry should
automatically log cohosting and fuse status as properties?
Turns out the code path is the same for OOP, whether precise ranges is
on or not :)

One of the items in #10103

Part of #9519
@davidwengier davidwengier requested a review from a team as a code owner March 20, 2024 22:12
@davidwengier davidwengier changed the base branch from dev/dawengie/CohostOOP to main March 20, 2024 22:12
@davidwengier davidwengier enabled auto-merge March 20, 2024 22:13
@davidwengier davidwengier merged commit 6bdc5c5 into main Mar 20, 2024
12 checks passed
@davidwengier davidwengier deleted the dev/dawengie/FilePathService branch March 20, 2024 22:51
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Mar 20, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants