-
Notifications
You must be signed in to change notification settings - Fork 332
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
change: [M3-7584] - Update react-router-dom
in preparation for React 18
#10154
change: [M3-7584] - Update react-router-dom
in preparation for React 18
#10154
Conversation
* @example "/profile/display" | ||
* @example "https://linode.com" | ||
*/ | ||
to: string; |
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.
@abailly-akamai Curious to see what you think about this because you most recently revamped this component.
We could write some logic to handle all cases of to: H.LocationDescriptor<S> | ((location: H.Location<S>) => H.LocationDescriptor<S>)
, but I think this might be a more desirable approach for now.
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.
I agree - it matches our current linking conventions and url matching so unless we have a need to pass anything else am happy to keep it overridden for strings only
Coverage Report: β
|
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.
π
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.
Thanks!
- e2e suites are passing
- no regressions found while testing the UI
* @example "/profile/display" | ||
* @example "https://linode.com" | ||
*/ | ||
to: string; |
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.
I agree - it matches our current linking conventions and url matching so unless we have a need to pass anything else am happy to keep it overridden for strings only
Description π
Updates
react-router-dom
(and its types) to the latest v5 version for React 18 compatibility π¦This should get us one step closer to React 18
How to test π§ͺ
As an Author I have considered π€