Include 'id' in datastore read #30
Closed
Conversation
This file contains 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
The datastore 'id' returned in the datastore read response should be the same as the 'id' used in the GET request. Nevertheless we use the returned value, mainly to detect the extremely unlikely case where the API returns an unexpected 'id' value.
stuart-mclaren-hpe
force-pushed
the
write-id
branch
from
227f6fe
to
52129e5
Compare
ZoeySimone
approved these changes
Aug 27, 2024
|
Closing - let's think about if we want to error here if there is a miss-match. |
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.
The datastore 'id' returned in the datastore read
response should be the same as the 'id' used in the GET request.
Nevertheless we use the returned value, mainly to detect the
extremely unlikely case where the API returns an unexpected 'id' value.