Skip to content
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

report: auto mode and when to show the report #459

Closed
dberenbaum opened this issue Feb 7, 2023 · 2 comments · Fixed by #684
Closed

report: auto mode and when to show the report #459

dberenbaum opened this issue Feb 7, 2023 · 2 comments · Fixed by #684
Labels
A: report Area: `live.make_report` p3-nice-to-have question Further information is requested

Comments

@dberenbaum
Copy link
Collaborator

#432 introduces report="notebook". Turning this on automatically may be too aggressive for some, but others may never discover it if we turn it off by default. I also expect that users rely less on the report now that we have other ways to show live updates, like in the VS Code extension or even Studio.

Do we still need auto mode at all? Should it be the default? What should its behavior be? It gives an obvious intro to the reports DVCLive can generate, and it can always be turned off, but I don't think it's behavior is obvious, and adding more report types to it only makes it more complicated.

@dberenbaum dberenbaum added the question Further information is requested label May 1, 2023
@daavoo
Copy link
Contributor

daavoo commented May 30, 2023

I was thinking that for 3.0 I would prefer the default to be None, drop html creation by default.

@dberenbaum
Copy link
Collaborator Author

Yup, I'm fine with that.

@daavoo daavoo mentioned this issue Sep 4, 2023
@daavoo daavoo added the A: report Area: `live.make_report` label Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: report Area: `live.make_report` p3-nice-to-have question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants