Handle 409 conflict error in overwrite function #101
Merged
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
Added specific handling for HTTP 409 conflict errors in the overwrite function to trigger a custom event with conflict details. This improves error reporting when attempting to overwrite an object that has a version conflict.
Enhanced the overwrite route to better handle errors, including 409 version conflicts, and to support the If-Overwritten-Version header from both request headers and the request body. Also improved validation for record IDs and refactored response handling for clarity.
thehabes
approved these changes
Jul 8, 2025
Member
thehabes
left a comment
thehabes
left a comment
There was a problem hiding this comment.
Manually tested using TalendAPI (to make requests to TinyNode) as well as the TinyNode interface. Added some touch ups to get things through as expected, added the token overhead back into overwrite.
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.
Added specific handling for HTTP 409 conflict errors in the overwrite function to trigger a custom event with conflict details. This improves error reporting when attempting to overwrite an object that has a version conflict.
This is done in TinyPEN correctly, but TinyThings receives a 409 and changes it to a 500 without helpful notes.