fix: fetch race condition #326
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves a race condition triggered during MCP page re-renders, for example, when opening the YAML splitter from the MCP header.
The reason was that
useApiResource
used the SWR key[resource.path, apiConfig]
while fetching the same MCP resource with different configs (depending onexcludeMcpConfig
being true/false). Because both responses shared the same SWR key, the full response occasionally overwrote the smaller one in the cache. This lead to issues when expected fields were missing.I now added
excludeMcpConfig
to the SWR cache key, so we have separate entries in the cache.