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

Enable TreatWarningsAsErrors for some projects #2150

Merged
merged 3 commits into from
Jan 2, 2020

Conversation

Bond-009
Copy link
Member

Analyzers are only run in debug build, so setting TreatWarningsAsErrors
for release build will catch the compiler warnings until we resolve all
analyzer warnings.

Analyzers are only run in debug build, so setting TreatWarningsAsErrors
for release build will catch the compiler warnings until we resolve all
analyzer warnings.
Copy link
Member

@EraYaN EraYaN left a comment

Choose a reason for hiding this comment

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

Looks good although maybe move the CS1591 and SA1600 disabled warnings to a rule file (not necessarily the main one).

@Bond-009
Copy link
Member Author

@EraYaN They are only being added to files that aren't documented 100%, this way new files are required to have full documentation.

@dkanada dkanada merged commit fb61a1f into jellyfin:master Jan 2, 2020
@Bond-009 Bond-009 deleted the releaseerror branch January 2, 2020 11:12
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.

None yet

3 participants