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
Every framework/lib is as good as the tools supporting its development. A devtools plugin for (initially) chrome would help to reduce the adoption friction of Arbor. Here are some ideas for features:
Time travel out-of-the-box: Anyone should be able to choose to start recording state mutations on an Arbor app and be able to replay them, or travel back and forth in time, and export the recording so other user may import and replay those mutations on their machine.
3D timeline to represent app mutations over time. Each mutations would render the entier app on a given z-index, allowing users to move back and forth in time, visualizing the different state snapshots taken during that period.
Live state tree rendering and path access highlighting. There should be a panel within the devtool where a tree data structure can be rendered to represent the current app state. As the dev access state within the tree via the dot notation API (store.state.users[0].name) the accessed path within the tree is highlighted.
The text was updated successfully, but these errors were encountered:
Every framework/lib is as good as the tools supporting its development. A devtools plugin for (initially) chrome would help to reduce the adoption friction of Arbor. Here are some ideas for features:
store.state.users[0].name
) the accessed path within the tree is highlighted.The text was updated successfully, but these errors were encountered: