-
Notifications
You must be signed in to change notification settings - Fork 7
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
Migrate business details page to React Router #6416
Migrate business details page to React Router #6416
Conversation
Passing run #50222 ↗︎Details:
Review all test suite changes for PR #6416 ↗︎ |
033e26a
to
2e5b56b
Compare
2e5b56b
to
3f47703
Compare
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👍
}) => { | ||
const { companyId } = useParams() | ||
return ( | ||
<CompanyResource id={companyId}> |
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.
We shouldn't be using any Resource
at root, the layout has to come first. By using the Resource
as root the entire page is blank until the API has responded. We don't want blank pages during an API request(s). Please take a look at Peter's recent work to understand how things have changed.
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.
Can you please point me to an example of where this new approach has been merged into main
as I am not able to find anything matching this description in the last few PRs.
1c4faae
into
feature-merge/company-layout-refactoring
Description of change
The business details page has now been migrated onto React Router.
Test instructions
The business details page should load as before
Checklist