docs: fetch-nearest starts from an external id too - #67
Open
olavgg wants to merge 1 commit into
Open
Conversation
Platform branch fix/fetch-nearest-external-id makes POST /resources/fetch-nearest honour the externalId its form always declared; an externalId-only request used to reach the repository with a null id and come back as a 500. The page carried a caution saying the field was accepted but not read, and a table row saying numeric id only. Both are now wrong for the endpoint and for the Java form, so the caution goes and the row matches fetchRelated's. The Python and Rust clients still build the request from a numeric id alone, so the resolve-with-by_ids advice stays, scoped to them, and the example comments say which client the constraint belongs to rather than blaming the endpoint. Verified: npm run build succeeds. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Olav Gjerde <olav@intellistream.ai>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Platform branch fix/fetch-nearest-external-id makes POST /resources/fetch-nearest honour the externalId its form always declared; an externalId-only request used to reach the repository with a null id and come back as a 500.
The page carried a caution saying the field was accepted but not read, and a table row saying numeric id only. Both are now wrong for the endpoint and for the Java form, so the caution goes and the row matches fetchRelated's. The Python and Rust clients still build the request from a numeric id alone, so the resolve-with-by_ids advice stays, scoped to them, and the example comments say which client the constraint belongs to rather than blaming the endpoint.
Verified: npm run build succeeds.