-
Notifications
You must be signed in to change notification settings - Fork 29
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
feat: add navigation visualizer to the react-navigation plugin #55
base: main
Are you sure you want to change the base?
Conversation
feat: add navigation stack visualizer to the react-navigation
fix: rename webui of navigation tree tab
feat: handle tab selection
fix: correct tab selection index
* feat: add scrolling behavior to the navigation tree * bump: bump version to handle scroll
migrate react-navigation-visualizer-dev-plugin to a bam.tech repo
* feat: add bamlab repo as a link to the npm package * docs: add illustration for navigation visualizer
* feat: improve scrolling behavior - make stack start from the bottom * bump: bump version to improve scrolling
that's amazing! |
Hey Kudo, thanks ! |
* feat: use navigation visualizer * feat: add new pages to the example app
* feat: remove top of the stacks to distinguish stacks better * feat: add space between each color for better distinction * feat: represent tabs by stacking pages horizontally * feat: represent selected tab by a dotted border * feat: add a legend to clarify the used objects
* feat: update docs with last visualizer features * bump: bump npm version
Why
The goal is to help developers debug their navigation state with an easy to understand representation.
How
I added a new tab in the react-navigation tool, based on what was already done in the two other tabs. The navigation state is retrieved from the plugin's store, recursively browsed to represent each stack, screen, and tab.
I temporarily renamed the package to be able to deploy it on our side.
What
The window goes as follows, showing two consecutive navigation states:
Identified next steps