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

Make rule 111 consistent to 109 #765

Closed
ePaul opened this issue Jun 13, 2023 · 2 comments
Closed

Make rule 111 consistent to 109 #765

ePaul opened this issue Jun 13, 2023 · 2 comments

Comments

@ePaul
Copy link
Member

ePaul commented Jun 13, 2023

  • Guideline 109 describes a conservative approach to API design – servers are supposed to reject unknown properties in inputs.
  • Guideline 111 says that "servers may reject requests whose entities contain undefined fields".

This sentence (and the following one) should be changed to match the approach in rule 109 (and also link to it).

@pablosaraiva
Copy link

pablosaraiva commented Jan 4, 2024

  • Guideline 109 describes a conservative approach to API design – servers are supposed to reject unknown properties in inputs.
  • Guideline 111 says that "servers may reject requests whose entities contain undefined fields".

This sentence (and the following one) should be changed to match the approach in rule 109 (and also link to it).

Both links point to guideline 109.

Here is suggested edit to the issue:

Guideline 111

@ePaul ePaul assigned ktsypkina and unassigned ePaul and SmilyOrg Jan 23, 2024
@ktsypkina
Copy link
Member

raised a PR with suggested changes, please have a look!
#793

@ePaul ePaul closed this as completed Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants