-
Notifications
You must be signed in to change notification settings - Fork 10
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
Slight ParsedRawReport
cleanup
#932
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #932 +/- ##
==========================================
- Coverage 97.97% 97.97% -0.01%
==========================================
Files 446 446
Lines 35657 35606 -51
==========================================
- Hits 34935 34884 -51
Misses 722 722
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
📢 Thoughts on this report? Let us know! |
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
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.
Well LGTM, but truth is I don't have too much context on this part of the code.
I left some questions, but they seem nit-level
return LegacyParsedRawReport( | ||
toc=toc_section, | ||
env=env_section, |
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.
Will we have to update documentation by removing this?
(Not against the removal, just trying to be helpful)
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.
which documentation do you mean?
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.
haha good point. I looked for docs mentioning this "env" options in the uploads but found none.
The only place you'd find is running --help
on the do-upload
command of the CLI honestly
Removes a bunch of has/get methods in favor of accessing fields directly. Removes the `env` field completely. Avoids a `BytesIO` indirection in the renamed `as_readable` method.
6ba6bba
to
3ba6405
Compare
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
This reverts commit 1d68d39.
Removes a bunch of has/get methods in favor of accessing fields directly. Removes the
env
field completely.Avoids a
BytesIO
indirection in the renamedas_readable
method.