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

Add flag to enable -warnings-as-errors Swift complier option #50

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pauljohanneskraft
Copy link

Add flag to enable -warnings-as-errors Swift complier option

♻️ Current situation & Problem

Currently, there is no option to enable the -warnings-as-errors Swift compiler option, which is potentially required by this PR.

⚙️ Release Notes

  • Adds warningsAsErrors flag to the build-and-test workflows to enable the respective -warnings-as-errors Swift compiler option. If not provided, the behavior remains the same as before.

📚 Documentation

  • Description for the warningsAsErrors parameter has been provided.

✅ Testing

I couldn't test this yet, as I'm not sure what the workflow would be.

📝 Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

Copy link
Member

@PSchmiedmayer PSchmiedmayer left a comment

Choose a reason for hiding this comment

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

@pauljohanneskraft Thank you for adding this here! It would be great if we can

  1. Test this version of the GitHub action by pointing the workflow references in Enable Strict Concurrency Checking Spezi#104 to this feature branch (you can use @feature/warnings-as-errors in the workflow files) to verify that is behaving as expected
  2. Finish up the Spezi by checking that warnings are detected as expected and things are passing when we have no warnings left.
  3. Merge this PR
  4. Update the Spezi PR to point to the release version of this GitHub action & merge the PR.

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.

2 participants