Skip to content
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

Optimize Destination loading and usage on destination item pages #21667

Closed
krishnaglick opened this issue Jan 20, 2023 · 0 comments · Fixed by #22068
Closed

Optimize Destination loading and usage on destination item pages #21667

krishnaglick opened this issue Jan 20, 2023 · 0 comments · Fixed by #22068
Assignees
Labels
area/frontend Related to the Airbyte webapp team/platform-move

Comments

@krishnaglick
Copy link
Contributor

DestinationItemPage, DestinationOverviewPage, and DestinationSettingsPage all make the same call to useGetDestination.
We can take the destination loaded on the DestinationItemPage and provide it through the outlet to the settings and overview pages.

Outlet Context
<Outlet context={{ destination }} />
const { destination } = useOutletContext<{ destination: DestinationRead }>();

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend Related to the Airbyte webapp team/platform-move
Projects
None yet
2 participants