-
Notifications
You must be signed in to change notification settings - Fork 177
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
Fix(Automate): CNX-8610 automate sdk warnings #3132
Conversation
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.
Super nice overall! O warnings
🙌🏼 Just have some comments on a couple things
Automate/Tests/Speckle.Automate.Sdk.Tests.Integration/GetAutomationStatus.cs
Show resolved
Hide resolved
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.
One last change please. Can you uncomment these lines in the automate csproj
<!-- <PropertyGroup Condition="'$(IsDesktopBuild)' == false">--> | |
<!-- <TreatWarningsAsErrors>true</TreatWarningsAsErrors>--> | |
<!-- </PropertyGroup>--> |
And also copy these lines to the automate test project.
These will make any warnings fail in CI, so there's no chance of any warnings being shipped now once this change is made!
...e/Tests/Speckle.Automate.Sdk.Tests.Integration/Speckle.Automate.Sdk.Tests.Integration.csproj
Outdated
Show resolved
Hide resolved
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.
My comments are resolved,
Ty @oguzhankoral
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.
Approving this! 🚀
Fixing all warnings on Automate.SDK and it's test project. And added README for test project.