-
Notifications
You must be signed in to change notification settings - Fork 177
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
NFC: enforce style for C# locally and on CI #1567
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.
This all looks reasonable, I assume all the code changes were because the style checker
was complaining?
@@ -176,7 +176,7 @@ public void Initialize(IncrementalGeneratorInitializationContext context) | |||
transform: (context, ct) => | |||
{ | |||
var tableSyntax = (TypeDeclarationSyntax)context.TargetNode; | |||
var table = context.SemanticModel.GetDeclaredSymbol(tableSyntax)!; | |||
var table = context.SemanticModel.GetDeclaredSymbol(tableSyntax, ct)!; |
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 looks like an actual runtime change, yes? Why is that?
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 removed the no-runtime-change
label)
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.
Well as it's purely codegen, technically it's still compile-time change, and one that shouldn't matter at that... but I don't have a strong opinion on that.
b4e03c5
to
d660a04
Compare
Unlike `dotnet` CLI, it doesn't like folder path and needs an explicit wildcard instead.
d660a04
to
66fe192
Compare
Description of Changes
As suggested in the other PR, adds C# style checks to the CI so that minor issues and reformatting are fixed early.
API and ABI breaking changes
If this is an API or ABI breaking change, please apply the
corresponding GitHub label.
Expected complexity level and risk
1
How complicated do you think these changes are? Grade on a scale from 1 to 5,
where 1 is a trivial change, and 5 is a deep-reaching and complex change.
This complexity rating applies not only to the complexity apparent in the diff,
but also to its interactions with existing and future code.
If you answered more than a 2, explain what is complex about the PR,
and what other components it interacts with in potentially concerning ways.
Testing
Describe any testing you've done, and any testing you'd like your reviewers to do,
so that you're confident that all the changes work as expected!