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

fix: avoid using global runtime in loader funciton #6280

Closed
wants to merge 2 commits into from

Conversation

AdityaHegde
Copy link
Collaborator

We were setting the global runtime in project's loader function and using it in explore's loader function to fetch explore spec and other data. This would cause issue with preloading routes where loader function gets called. Hovering over other projects in breadcrumbs would update the runtime causing the dashboard list to be incorrect.

Here we are making explicit calls to httpRuntime with a custom Runtime object. This should not be the final solution since changes to API is not auto generated. We should look at autogenerating these fetch wrappers for every API.

@AdityaHegde AdityaHegde added the blocker A release blocker issue that should be resolved before a new release label Dec 16, 2024
@AdityaHegde AdityaHegde force-pushed the fix/runtime-init-in-loader branch from 7374789 to 86275ba Compare December 16, 2024 13:33
@AdityaHegde
Copy link
Collaborator Author

We are opting to disable preload on links to other projects in the breadcrumbs and any other places.

@AdityaHegde AdityaHegde deleted the fix/runtime-init-in-loader branch December 16, 2024 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker A release blocker issue that should be resolved before a new release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant