Navigating to next / previous graphs - regardless of filter

[EatingW]

Poker planning notes:

• When user navigate to next / previous graph, apply the mutation to the graph
• Is this applicable to jumping to steps?
  • This is a separate task (timeline view)
• Use case: navigate to next/previous in a filtered graph.
• Currently mutations is stored as a list
• Send mutation to client vs send graph to client?
  • right now the client does not do graph transformation
  • for MVP just send the mutated graph over
• For previous button how to recover previous state? e.g. metadata, deleting a node?
  • naive solution to always apply the mutations from the initial graph
  • optimization can be a separate task
• Steps:
  • client side add next/prev arrows
  • counter for current mutation step
  • server apply mutation to graph
  • send updated graph to client
  • How to consider done:
  • Demo of clicking prev/next
  • Verify the client send the right next/prev request
  • Unit tests on the server side for applying the mutations

Proposed estimate: 4