feat(134): replace etag guidance with 154 reference#356
Merged
toumorokoshi merged 1 commit intoaep-dev:mainfrom Sep 30, 2025
Merged
feat(134): replace etag guidance with 154 reference#356toumorokoshi merged 1 commit intoaep-dev:mainfrom
toumorokoshi merged 1 commit intoaep-dev:mainfrom
Conversation
toumorokoshi
force-pushed
the
yft/fix-241
branch
from
77827b1 to
6b151ae
Compare
Previously, there was bespoke guidance in the Update AEP that refered to using a custom ETag field in the resource for validating previous resource state. This guidance somewhat duplicates the guidance in RFC 9110 and AEP-154 which states that it should be adhered to. This duplication can lead to partial support of both, which in turn will make client integration more difficult. Therefore, removing this guidance. Fixes aep-dev#241
toumorokoshi
force-pushed
the
yft/fix-241
branch
from
6b151ae to
a8e62d5
Compare
rambleraptor
approved these changes
Sep 29, 2025
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
2 participants
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.
Previously, there was bespoke guidance in the Update AEP that refered to using a custom ETag field in the resource for validating previous resource state.
This guidance somewhat duplicates the guidance in RFC 9110 and AEP-154 which states that it should be adhered to. This duplication can lead to partial support of both, which in turn will make client integration more difficult.
Therefore, removing this guidance. Fixes #241
🍱 Types of changes
What types of changes does your code introduce to AEP? Put an
xin the boxesthat apply
📋 Your checklist for this pull request
Please review the AEP Style and Guidance for
contributing to this repository.
General
references AEPs
correctly.
(usually
prettier -w .)./scripts/fix.py💝 Thank you!