Conversation
closes #5184 Required PR: pulp/pulp_file#272 Required PR: pulp/pulpcore-plugin#123 https://pulp.plan.io/issues/5184
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
Codecov Report
@@ Coverage Diff @@
## master #123 +/- ##
=========================================
- Coverage 42.68% 42.09% -0.6%
=========================================
Files 22 21 -1
Lines 738 727 -11
=========================================
- Hits 315 306 -9
+ Misses 423 421 -2
Continue to review full report at Codecov.
|
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
|
Does it make sense to create a pre-defined set of codes which will be likely used by plugins as well? The goal is to make it easier to have at least some consistency in the code names across plugins. E.g. sync, publish, parsing metadata, etc. |
@goosemania I believe it makes sense, but I don't know what would be these set of codes, and in some cases, it is hard to define what would be the code to differentiate the progress bars, like in this case: https://github.com/pulp/pulp_rpm/pull/1437/files |
CHANGES/5184.misc
Outdated
| @@ -0,0 +1 @@ | |||
| Adding `code` on `ProgressBar`. | |||
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.
This needs to probably be a feature.
| @@ -78,7 +78,7 @@ def __init__(self, new_version, *args, **kwargs): | |||
| Returns: | |||
| The coroutine for this stage. | |||
| """ | |||
| with ProgressBar(message='Un-Associating Content') as pb: | |||
| with ProgressBar(message='Un-Associating Content', code='un-associating.content') as pb: | |||
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.
s/un-associating/unassociating/
closes #5184 Required PR: pulp/pulp_file#272 Required PR: pulp/pulpcore-plugin#123 https://pulp.plan.io/issues/5184
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore#289 Required PR: pulp/pulp_file#272
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
closes #5184 Required PR: pulp/pulp_file#272 Required PR: pulp/pulpcore-plugin#123 https://pulp.plan.io/issues/5184
closes #5184 Required PR: pulp/pulp_file#272 Required PR: pulp/pulpcore-plugin#123 https://pulp.plan.io/issues/5184
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
ref #5184 https://pulp.plan.io/issues/5184 Required PR: pulp/pulpcore-plugin#123 Required PR: pulp/pulpcore#289
ref #5184
https://pulp.plan.io/issues/5184
Required PR: pulp/pulpcore#289
Required PR: pulp/pulp_file#272
Please be sure you have read our documentation on creating PRs:
https://docs.pulpproject.org/en/3.0/nightly/contributing/pull-request-walkthrough.html