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

Remove TreatWarningsAsErrors flags from local builds for developer convenience #28198

Merged

Conversation

frenzibyte
Copy link
Member

Has been discussed in here and here. This flag has been causing unnecessary hurdles with development, such as builds failing when using obsolete methods while temporarily testing changes, or when commenting code that cuts off all usages to a field/property/constant (this is especially frusturating with hot reload, because removing members is not fully supported, and the developer loses the point of having hot reload).

Our workflows already append the -warnaserror flag during builds, so all warnings are still treated as errors and fail CI (tested in here).

In addition, Rider does a pretty good job of warning developers if there are warnings in build, so that should not be a concern when removing this flag (missing warnings during a PR):

image

@smoogipoo smoogipoo merged commit 9532725 into ppy:master May 18, 2024
13 of 17 checks passed
@frenzibyte frenzibyte deleted the remove-warnaserror-from-local-builds branch May 18, 2024 04:54
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.

2 participants