-
Notifications
You must be signed in to change notification settings - Fork 14
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
Move report #481
Move report #481
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #481 +/- ##
==========================================
+ Coverage 70.46% 75.61% +5.15%
==========================================
Files 42 42
Lines 2966 2957 -9
==========================================
+ Hits 2090 2236 +146
+ Misses 876 721 -155
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
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.
LGTM, thanks!
Move the report part from the
submission
step to theresult
step, so that all the report-related parameters are handled in, and only in, the result step.The old design separates the report into two parts in the
submission
andresult
steps, which is hard to maintain. One also needs to save and reload the parameters. Which is a mess, as seen from the names of the functions._create_extra_report_parameters
,_extract_report_parameters
,_generate_report_dict
,_generate_report_html
,generate_report_html
It also extracts parameters from the GUI and the builder to form a
builder_parameters
, but later one needs to re-extract the GUI parameters back from thebuilder_parameters
(handle the logic again). Most importantly, we can not reload all GUI parameters, which is bad.The current implementation:
result
step, thesummary_viewer.py
file.ui_parameters
, and set it as an extra attribute to the node, so we can reload the GUI back.ui_parameters
and inputs of the workchain node directly.Test
result
step, including a regression test for the report parameters. +5 % now! 😀