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

studio: Segregate transaction browser code #358

Closed
3 tasks done
epost opened this issue Feb 19, 2020 · 0 comments
Closed
3 tasks done

studio: Segregate transaction browser code #358

epost opened this issue Feb 19, 2020 · 0 comments
Assignees
Labels
visualization visualize, render, UI

Comments

@epost
Copy link
Member

epost commented Feb 19, 2020

When clicking on a node in a diagram from the API, render it.

Segregate some code and types so we can easily split between studio and transaction browser functionality.

  • Introduce NetsAndDiagramsIndex newtype.
  • Segregate Routes into Statebox API things (wirings, firings, root, etc) into their own ApiRoute type.
  • Put model code relating to the transactions loaded into memory into their own TxCache module.

Based on reimagined wiring paths etc in #331.

@epost epost added the visualization visualize, render, UI label Feb 19, 2020
@epost epost self-assigned this Feb 19, 2020
@epost epost changed the title studio: Render API routes studio: Segregate transaction browser code Mar 6, 2020
epost added a commit that referenced this issue Mar 6, 2020
* studio: Segregate Routes to stbx core/API things into separate ADT. #358

* studio: Use NetsAndDiagramsIndex nwetype in Routes. #358

* studio: put Studio tx cache model stuff in a separate model. #358
@epost epost closed this as completed Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
visualization visualize, render, UI
Projects
None yet
Development

No branches or pull requests

1 participant