Skip to content

Conversation

@sharwell
Copy link
Contributor

@sharwell sharwell commented Mar 6, 2020

No description provided.

@sharwell sharwell requested a review from a team as a code owner March 6, 2020 18:25
Comment on lines 31 to 35
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 These were internal methods, so I just reverted a6d62cc and 1afb1c6 to use the original approach.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edit: Only EndOfLine was a problem.

@sharwell sharwell changed the title Move file header analyzer to the code style layer Share file header analyzer with the code style layer Mar 6, 2020
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM modulo @mavasani 's feedback.

Copy link
Contributor

@mavasani mavasani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, modulo switching back to ISyntaxFacts.ParseLeadingTrivia and reverting the added abstract method ParseLeadingTrivia

@mavasani
Copy link
Contributor

mavasani commented Mar 6, 2020

By the way, super excited with the prospect of enabling this analyzer and enforcing headers from CodeStyle NuGet package! @sharwell I think we do want #41687 to go in so we don't see duplicate diagnostics + execution from CodeStyle NuGet and built-in IDE analyzer

@sharwell sharwell force-pushed the shared-file-headers branch from f0a8fca to 4f54c77 Compare March 6, 2020 19:14
@sharwell sharwell merged commit 61ffa90 into dotnet:master Mar 6, 2020
@ghost ghost added this to the Next milestone Mar 6, 2020
@sharwell sharwell deleted the shared-file-headers branch March 6, 2020 21:47
@sharwell sharwell modified the milestones: Next, 16.6.P2 Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants