Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify ordering constraints of deleted entity in JSON payload #2013

Merged
merged 5 commits into from
Oct 16, 2024

Conversation

mikepizzo
Copy link
Contributor

Fixes #1985

ralfhandl
ralfhandl previously approved these changes Oct 16, 2024
Copy link
Contributor

@HeikoTheissen HeikoTheissen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Section 4.5 demands the order: context, removed, type, [etag, ] id
Section 15.3. demands the order: [context, ] removed, [type, ] id
Can section 15.3 instead refer to section 4.5?

Have section 15.3 refer to section 4.5 for ordering constraints.
HeikoTheissen
HeikoTheissen previously approved these changes Oct 16, 2024
@mikepizzo mikepizzo merged commit c54ac7f into main Oct 16, 2024
1 check passed
@mikepizzo mikepizzo deleted the odata1985 branch October 16, 2024 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify ordering of control information for deleted entity
3 participants