-
Notifications
You must be signed in to change notification settings - Fork 236
Support Task List in cohosting #12181
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
Changes from all commits
d74b5cd
7515709
acf2b76
2c31f2e
973705a
96eaf2a
3f0c113
5249100
a732a9a
5748658
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -21,5 +21,6 @@ ValueTask<ImmutableArray<LspDiagnostic>> GetTaskListDiagnosticsAsync( | |
| JsonSerializableRazorPinnedSolutionInfoWrapper solutionInfo, | ||
| JsonSerializableDocumentId documentId, | ||
| ImmutableArray<string> taskListDescriptors, | ||
| LspDiagnostic[] csharpTaskItems, | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No reason, thats just what the diagnostic translate service takes, presumably because it works directly on a deserialized LSP response, and I carried it through. Is it worth changing, other than for consistency?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not worth changing, just consistency and a general appreciation for using ImmutableArrays when possible |
||
| CancellationToken cancellationToken); | ||
| } | ||
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.
Out of curiosity, why not have this defined in version.details.props?
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.
I assume you meant "why not in Version.props", and the answer is this split came from arcade, so there was one version file for people, and one for automation. See dotnet/arcade-services#4998
The irony is of course, I've only ever manually updated this file, and its xml file twin.