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

.visualize_execution and .visualize_materialization shouldn't need inputs #1185

Closed
zilto opened this issue Oct 15, 2024 · 0 comments
Closed
Labels
enhancement New feature or request visualization

Comments

@zilto
Copy link
Collaborator

zilto commented Oct 15, 2024

When using Driver.visualize_execution() and Driver.visualize_materialization(), you need to specify inputs and overrides to determine the path from "inputs" to final_vars and display it.

A friction point is that users must specify a valid inputs dictionary to use this visualization (i.e., includes all the necessary inputs with the right types). Since inputs values aren't actually used, the logic could be reworked to assume that "all inputs are available`.

This would be a quality of life improvement

@zilto zilto changed the title visualization: ` visualization: .visualize_execution and .visualize_materialization shouldn't need inputs Oct 15, 2024
@zilto zilto changed the title visualization: .visualize_execution and .visualize_materialization shouldn't need inputs .visualize_execution and .visualize_materialization shouldn't need inputs Oct 15, 2024
@zilto zilto added enhancement New feature or request visualization labels Oct 15, 2024
@zilto zilto closed this as completed Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request visualization
Projects
None yet
Development

No branches or pull requests

1 participant