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
TypeDefinition.js defines NavigationParams as a map where each value (parameter) must be a string.
export type NavigationParams = { [key: string]: string, };
Yet, in the same file there's a documented example, where the value is an int.
/**
* Params passed to this route when navigating to it,
* e.g. `{ car_id: 123 }` in a route that displays a car.
*/
To me it looks like NavigationParams type definition is wrong, but I couldn't be sure, since you may have thought about URL routing, where each parameter must be string.
The text was updated successfully, but these errors were encountered:
TypeDefinition.js defines
NavigationParams
as a map where each value (parameter) must be a string.export type NavigationParams = { [key: string]: string, };
Yet, in the same file there's a documented example, where the value is an int.
To me it looks like NavigationParams type definition is wrong, but I couldn't be sure, since you may have thought about URL routing, where each parameter must be string.
The text was updated successfully, but these errors were encountered: