-
Notifications
You must be signed in to change notification settings - Fork 906
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
Update PlotlyDataSet save method to accept Figure object #955
Conversation
CI is stuck with |
Looks like this PR is also facing the same issue... #960 |
I don't know what went wrong, but I just re-triggered the build. |
@MerelTheisenQB Thanks! Looks like only your commit (or commits from kedro core team) can trigger the CI... I've just pushed a new commit to fix the errors, and CI is now stuck again... |
@MerelTheisenQB Sorry, but could you trigger the CI one more time?... I've fixed the errors from the CI, so I think the PR is good to go. |
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.
Could someone from Kedro core team merge the PR (and trigger the CI as it's stuck again), please? |
Description
As discussed in Slack, it's better for this dataset to accept Figure object for both save and load methods (at the moment,
_save
accepts dataframe whereas_load
loads Figure object, which is a inconsistent API for users).This change is a minor breaking change unfortunately, so I'm opening the PR against develop branch.
Development notes
Checklist
RELEASE.md
fileNotice
I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":
I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.