You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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)
The text was updated successfully, but these errors were encountered:
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.
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
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)
The text was updated successfully, but these errors were encountered: