Use identifier value in remote custom field cache key #107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ngaspari
approved these changes
Sep 12, 2025
ngaspari
deleted the
use_identifier_value_in_remote_custom_field_cache_key
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Imagine you have implemented a remote custom field that fetches the first 50 results.
You retrieve those initial 50 results, and then attempt to resolve a record with an identifier value of 1234.
Since that record is not among the first 50, the backend returns an empty object — indicating that the record was not found.
To fix this behavior, the identifier value should be included in the cache key for the remote custom field.