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

Treat Build Warnings as Errors for Abstractions & DependencyInjection Projects #4050

Merged
merged 11 commits into from
Sep 10, 2020

Conversation

SkyeHoefling
Copy link
Contributor

Fixes #4040

Summary

This PR updates DotNetNuke.Abstractions and DotNetNuke.DependencyInjection to treat all build warnings as errors. This will help ensure a high level of code quality in these new projects.

@SkyeHoefling SkyeHoefling changed the title Build warnings Treat Build Warnings as Errors for Abstractions & DependencyInjection Projects Sep 4, 2020
Copy link
Contributor

@bdukes bdukes left a comment

Choose a reason for hiding this comment

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

💪🏻

DNN Platform/DotNetNuke.Abstractions/Prompt/ICommand.cs Outdated Show resolved Hide resolved
@@ -1,33 +1,38 @@
// Licensed to the .NET Foundation under one or more agreements.
// The .NET Foundation licenses this file to you under the MIT license.
// See the LICENSE file in the project root for more information

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this blank line required? I had been removing this line. I'm fine either way, just wondering if I was working against StyleCop when I was doing that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is not a stylecop setting, for some reason I thought it was inside our stylecop configuration. I can remove these blank lines below the file header.

Copy link
Contributor Author

@SkyeHoefling SkyeHoefling Sep 4, 2020

Choose a reason for hiding this comment

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

To be clear, what would the reviewers like me to do here? White space or no white space

Copy link
Contributor

Choose a reason for hiding this comment

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

I would prefer no white space, but happy to be overridden if there are any other opinions

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have removed the whitespace, I'm going to leave this conversation open if anyone has strong opinions on this

Co-authored-by: Brian Dukes <bdukes@engagesoftware.com>
@bdukes bdukes added this to the 9.7.2 milestone Sep 4, 2020
@valadas
Copy link
Contributor

valadas commented Sep 5, 2020

image

@david-poindexter
Copy link
Contributor

OMG @valadas - who does that??????? 🤣

Copy link
Contributor

@valadas valadas 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 to me

@valadas valadas merged commit 8691bee into dnnsoftware:develop Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Treat Warnings as Build Errors - DotNetNuke.Abstractions
4 participants