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

Default visualizations should be chosen based on a value's to_default_visualization_data. #5195

Closed
wdanilo opened this issue Feb 5, 2023 · 2 comments
Labels
-viz p-low Low priority x-new-feature Type: new feature request

Comments

@wdanilo
Copy link
Member

wdanilo commented Feb 5, 2023

This task is automatically imported from the old Task Issue Board and it was originally created by Michael Mauderer.
Original issue is here.


Why

Better experience when exploring the output of nodes, as information will be presented in a more appropriate way.

As User
**I want ** the best possible visualization appear for every node
**So that ** I can make sense of the node's output

Acceptance Criteria

Scenario: 
Given I have a project that contains a node with some data, e.g., of type `Table` or `Image`
When I open the visualisation
Then I see the best possible visualisaiton for the data (i.e., Table Visualisation or Image Visualisation)

Notes:
See old issues related to this here: #2951

Note that this is related, but not completely duplicate to https://www.pivotaltracker.com/story/show/184245839
However, both need a lot of similar preliminary work on the IDE controller side to be implemented (one-shot expressions, and using those to determining valid visualizations)

@jdunkerley
Copy link
Member

Please note the method default_visualization provides the name for the standard visualization for a value. This could be merged into to_default_visualization_data.

@farmaazon
Copy link
Contributor

Implemented in GUI2

@farmaazon farmaazon closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-viz p-low Low priority x-new-feature Type: new feature request
Projects
None yet
Development

No branches or pull requests

3 participants