Skip to content

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

Merged
merged 9 commits into from
Dec 7, 2022

Conversation

bkonyi
Copy link
Contributor

@bkonyi bkonyi commented Nov 28, 2022

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 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.
@bkonyi bkonyi requested review from elliette, kenzieschmoll and a team as code owners November 28, 2022 16:02
@bkonyi bkonyi requested a review from polina-c as a code owner December 7, 2022 16:15
Copy link
Member

@kenzieschmoll kenzieschmoll left a 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?

Copy link
Member

@elliette elliette left a 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!

@bkonyi
Copy link
Contributor Author

bkonyi commented Dec 7, 2022

Filed #4902 for future integration testing.

@bkonyi bkonyi merged commit faaeb62 into flutter:master Dec 7, 2022
@bkonyi bkonyi deleted the profiler_jump_to_source branch December 7, 2022 17:58
@bkonyi bkonyi mentioned this pull request Dec 7, 2022
CoderDake pushed a commit that referenced this pull request Dec 9, 2022
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants