-
Notifications
You must be signed in to change notification settings - Fork 344
Add initial support for non-query param navigation state #4837
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
Conversation
This change adds support for providing additional state when navigating through DevTools via `DevToolsRouterDelegate` without polluting the query parameters with extra entries. This state is included in the navigation history. Controllers can mixin the new `RouteStateHandlerMixin` and override `onRouteStateUpdate(DevToolsNavigationState)` to handle changes in the current DevTools navigation state. To handle state changes, `subscribeToRouterEvents` must first be called on the controller. This change also adds support for jumping to a source location in the debugger from URIs in the CPU profiler.
packages/devtools_app/lib/src/screens/debugger/codeview_controller.dart
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more comment then LGTM. Can you also add a TODO and file an issue to add an integration test that uses the chrome back / forward buttons once we can run integration tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for debugger screen changes!
Filed #4902 for future integration testing. |
This change adds support for providing additional state when navigating through DevTools via `DevToolsRouterDelegate` without polluting the query parameters with extra entries. This state is included in the navigation history. Controllers can mixin the new `RouteStateHandlerMixin` and override `onRouteStateUpdate(DevToolsNavigationState)` to handle changes in the current DevTools navigation state. To handle state changes, `subscribeToRouterEvents` must first be called on the controller. This change also adds support for jumping to a source location in the debugger from URIs in the CPU profiler.
This change adds support for providing additional state when navigating through DevTools via
DevToolsRouterDelegate
without polluting the query parameters with extra entries. This state is included in the navigation history.Controllers can mixin the new
RouteStateHandlerMixin
and overrideonRouteStateUpdate(DevToolsNavigationState)
to handle changes in the current DevTools navigation state. To handle state changes,subscribeToRouterEvents
must first be called on the controller.This change also adds support for jumping to a source location in the debugger from URIs in the CPU profiler.