-
-
Notifications
You must be signed in to change notification settings - Fork 198
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 configuration option fail_on_warnings
#23
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.
Thanks for adding this! Mostly good, just a few wording changes.
Also please do test the command line argument, and add an entry to the CHANGELOG.
Awesome thanks, could you add a changelog entry too? |
I'm testing the command line argument at the moment and will add a CHANGELOG entry if no issues arise. Stay tuned ... |
Do the command line arguments matter if there's a configuration file already? Cause it didn't work in my project when running project: NewProjectTemplate.xcodeproj
schemes: [App]
targets: [App, Tests, UITests]
report_exclude:
- App/Generated/SwiftGen/*.swift
- App/SupportingFiles/*.swift
retain_public: false
quiet: true Running project: NewProjectTemplate.xcodeproj
schemes: [App]
targets: [App, Tests, UITests]
report_exclude:
- App/Generated/SwiftGen/*.swift
- App/SupportingFiles/*.swift
retain_public: false
strict: true
quiet: true |
Ah yes, you need to populate the configuration for command-line options. You'll need to do this in both |
Makes sense, I added it as suggested to both. Testing now ... will report once done. Please note that I already added a CHANGELOG entry and used the conventions from the SwiftGen project (see their CHANGELOG) and the SwiftLint project (theirs) here, too since there's none yet. Feel free to change the structure if you want to use a different style, I just thought since this open sourced very recently you might not have thought about one yet. |
Yes, it works both with |
CHANGELOG format looks good 👍 |
@ileitch Thanks for reviewing and merging so quickly. 👍 Unfortunately the CHANGELOG doesn't seem to render like in the linked documents, where everything is on one line, but here it uses mutiple lines ... dunno why, but can be fixed over time, shouldn't be a huge problem. 😅 |
Yep no worries, thanks for the submission! |
This is a naive fix for #22. I tested this by installing my fork via Mint and it worked. I'm not sure if this is complete though, as I didn't write any tests or check if this also works as command line argument directly (I just tested via configuration file).