-
Notifications
You must be signed in to change notification settings - Fork 173
Conversation
|
How will this affect things like classes being marked as deprecated? I know we generally try to not to use deprecated structures, but sometimes during multi-part work it's convenient to add the new infrastructure, mark the old one as deprecated, and then go around update all the consumers. EDIT: never mind, I realize now that we can just put specific suppressions in if there needs to be that kind of delay between deprecation and update :) |
|
Yeah, you can use |
cesarzc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this Sarah!
Updated the CI to build with
/property:TreatWarningsAsErrors=true. This means that warnings are allowed when developing locally, but all warnings must be fixed or suppressed before a PR can be merged.This applies to C# and F# warnings, but not MSBuild and Q# warnings.