close
The Wayback Machine - https://web.archive.org/web/20210209052934/https://github.com/microsoft/reverse-proxy/pull/19
Skip to content
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

Style fix ups #19

Merged
merged 8 commits into from Mar 17, 2020
Merged

Style fix ups #19

merged 8 commits into from Mar 17, 2020

Conversation

@anurse
Copy link
Contributor

@anurse anurse commented Mar 14, 2020

A whole bunch of style fix ups. I tried to make each commit a separate fix-up so it can be reviewed a little better.

I'm not expecting an in-depth review, just making sure something didn't get completely haywire.

Fixes #6

@anurse anurse requested a review from halter73 Mar 14, 2020
@@ -1,3 +1,4 @@
# Suppress: EC103

This comment has been minimized.

@halter73

halter73 Mar 16, 2020
Member

Can we add a comment explaining what EC103 is? Looks like we have some file globbing patterns that don't match any files yet, but it took me a sec to find the doc.

This comment has been minimized.

@anurse

anurse Mar 16, 2020
Author Contributor

Yeah... I might just either fix that up or remove the suppression entirely. It only shows up if you're using the EditorConfig Extension for VS.

@@ -1,3 +1,4 @@
# Suppress: EC103
; EditorConfig to support per-solution formatting.

This comment has been minimized.

@halter73

halter73 Mar 16, 2020
Member

I tried checking this branch out locally and looking at the .editorconfig file and VS gave me warnings about inconsistent line endings. Can we copy in the .gitattributes file from the aspnetcore repo to avoid this?

This comment has been minimized.

@anurse

anurse Mar 16, 2020
Author Contributor

Sure, good plan.

}

public void ReportError(string code, string itemId, string message)
{
this.logger.LogWarning($"Config error: '{code}', '{itemId}', '{message}'.");
_logger.LogWarning($"Config error: '{code}', '{itemId}', '{message}'.");

This comment has been minimized.

@BrennanConroy

BrennanConroy Mar 17, 2020
Member

We need to fix these 😆

This comment has been minimized.

@anurse

anurse Mar 17, 2020
Author Contributor

Good catch, I can make a pass over them.

This comment has been minimized.

@anurse

anurse Mar 17, 2020
Author Contributor

Actually we should probably assign EventIds and such. I'll file a bug.

This comment has been minimized.

@anurse

anurse Mar 17, 2020
Author Contributor

#20

@anurse anurse merged commit b2cf5bd into master Mar 17, 2020
1 check passed
1 check passed
license/cla All CLA requirements met.
Details
@anurse anurse deleted the anurse/style-fix-up branch Mar 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

3 participants