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
The ReactNavigationIntegration doesn't read dispatch action data and starts generic Route Changed navigation span on every dispatch.
Depending on the action type the new route name can be specified in the data. For example navigation action has name of the new route in it's payload. This might not be the final route as that depends on the router processing the action.
Using the data from the dispatched action will reduce the number of Route Changed spans. We should still update the name once the router processed the action with the final route name.
The ReactNavigationIntegration doesn't read dispatch action data and starts generic
Route Changed
navigation span on every dispatch.Depending on the action type the new route name can be specified in the data. For example navigation action has
name
of the new route in it's payload. This might not be the final route as that depends on the router processing the action.Using the data from the dispatched action will reduce the number of
Route Changed
spans. We should still update the name once the router processed the action with the final route name.current integration implementation
react-navigation onDispatch implementation
poc branch
Related Issue: not all actions are expected to trigger navigation
The text was updated successfully, but these errors were encountered: