-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[WIP] plots: html_template -> html #6221
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -45,7 +45,7 @@ def run(self): | |||||
| rel: str = self.args.out or "plots.html" | ||||||
| path = (Path.cwd() / rel).resolve() | ||||||
| self.repo.plots.write_html( | ||||||
| path, plots=plots, html_template_path=self.args.html_template | ||||||
| path, plots=plots, html_template_path=self.args.html | ||||||
| ) | ||||||
|
|
||||||
| except DvcException: | ||||||
|
|
@@ -249,8 +249,8 @@ def _add_output_arguments(parser): | |||||
| help="Open plot file directly in the browser.", | ||||||
| ) | ||||||
| parser.add_argument( | ||||||
| "--html-template", | ||||||
| "--html", | ||||||
| default=None, | ||||||
| help="Custom HTML template for VEGA visualization.", | ||||||
| help="Custom HTML for VEGA visualization.", | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| metavar="<path>", | ||||||
| ) | ||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -225,5 +225,5 @@ class RelPath(str): | |
| # enabled by default. It's of no use, kept for backward compatibility. | ||
| Optional("parametrization", default=True): Bool | ||
| }, | ||
| "plots": {"html_template": str}, | ||
| "plots": {"html": str}, | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can it compatible with the old schema? Some users might have an old version in their workspace.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is true, but the feature is relatively new and I think there is more harm in leaving
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we adopt the old version, and transfer it to new ones? Or at least give some friendly messages when it happens.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This feature was only introduced in the last minor version or so, and it was specifically developed for the Studio team, so I wouldn't expect many (probably any) other people are using it. Feel free to support both or whatever you think is best, but I don't think this is a breaking change worth worrying about.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. AFAIK @mnrozhkov is the person that needs to know about this change, also one user on discord. I will try to reach out to this user.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Studio guys will complain about problems with this, we should not break an already released schema. We have to keep older name, but we could introduce an alias.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My mistake, I didn't think it would be a big deal for studio.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Related feedback, for the record: #5694 (review) (for the alias) |
||
| } | ||
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 is backwards incompatible, right? Can we keep an alias or something?