-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
plots: upgrade to latest Vega library versions #6371
Conversation
related: #6218 as noted in that issue, if you need specific features you can define your own HTML template to override vega-lite version used in the default DVC templates |
@pmrowla Thanks for the suggestion, that's exactly what I'm doing right now. |
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.
I have manually checked the current existing templates. They seem to be working fine.
@arjvik can you rebase on current master? |
@pared done! |
@pared Seems like both automated and manual tests have passed... is this going to get merged? |
@arjvik sorry for the delay, yes I think we can merge it. |
Hi @pared should we do a super quick update to the example in https://dvc.org/doc/command-reference/plots#example-offline-html-template ? Also, that should be an H2 π (it's an H3 rn). Thanks |
@jorgeorpinel lets continue in iterative/dvc.org#2798 |
β I have followed the Contributing to DVC checklist.
[N/A] π If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
The current version of Vega included in the plots template page is quite outdated. Many of the features mentioned in the Vega Lite documentation are Vega-Lite 5.0 only, and thus fail to work on the 4.0 version included by DVC. I submitted this change that simply changes the version numbers to the latest versions released as of now.
One idea to consider is omitting the version entirely and allowing jsDelivr to pick the latest version it has available. Vega plots all require a
$schema
parameter that specifies the version of the Vega specification to adhere to when displaying, so even breaking changes to the latest spec should not cause issues to existing plots.