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

[wip] Improve handling missing coverage info #37

Closed
wants to merge 1 commit into from

Conversation

yhkaplan
Copy link

@yhkaplan yhkaplan commented Nov 9, 2021

ref: #25

# Output the processed report
output_report(report)
rescue => e
markdown("Xcov not run due to error: #{e}")
Copy link
Author

Choose a reason for hiding this comment

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

warn or fail is more appropriate than markdown method. Also, I had some string encoding issues with displaying the error... Maybe better to leave it out?

Xcov not run due to error: �[31mError creating your coverage report - see the log above�[0m

Copy link
Author

Choose a reason for hiding this comment

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

@nakiostudio @joshdholtz @ffittschen How do you think the error should be handled? I think rescuing a specific error type would make this plugin brittle and break functioning whenever xcov changes, but what do you think of outputting a generic error thusly:

error("Xcov-danger could not run")

Having the error info would make it easier to fix the problem, but I'm not sure where the string encoding issues are coming from...

@yhkaplan yhkaplan closed this Mar 25, 2022
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.

1 participant