Clarification on api-name, filenames and servers object #333
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
* Update API-design-guidelines.md * Update API-design-guidelines.md * Clarifications on api-name, filenames and servers object * Revert "Update API-design-guidelines.md" This reverts commit 1353c82. --------- Co-authored-by: rartych <rafal.artych@t-mobile.com>
rartych
requested review from
shilpa-padgaonkar,
patrice-conil,
RubenBG7 and
PedroDiez
as code owners
This was referenced Nov 6, 2024
gmuratk
reviewed
Nov 8, 2024
gmuratk
approved these changes
Nov 18, 2024
patrice-conil
requested changes
Nov 25, 2024
| @@ -927,7 +928,7 @@ And according to the filtering based on string and enums data, being searched fo | |||
| **Additional rules**: | |||
| - The operator "`&`" is evaluated as an AND between different attributes. | |||
| - A Query Param (attribute) can contain one or n values separated by "`,`". | |||
| - For operations on numeric, date or enumerated fields, the parameters with the suffixes `.(gte|gt|lte|lt)$` need to be defined, which should be used as comparators for “greater—equal to, greater than, smaller—equal to, smaller than” respectively. Only the parameters needed for given field should be defined e.g., with `.gte` and `.lte` suffixes only. | |||
| - For operations on numeric, date or enumerated fields, the parameters with the suffixes `.(gte|gt|lte|lt)$` need to be defined, which should be used as comparators for “greater—equal to, greater than, smaller—equal to, smaller than” ly. Only the parameters needed for given field should be defined e.g., with `.gte` and `.lte` suffixes only. | |||
There was a problem hiding this comment.
typo: only "ly" remains for respectively
There was a problem hiding this comment.
Corrected in 7c05167
rartych
dismissed stale reviews from shilpa-padgaonkar and PedroDiez
via
7c05167
patrice-conil
approved these changes
Nov 25, 2024
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.
What type of PR is this?
What this PR does / why we need it:
Missing guideline for file names of API definition files, indirect definition of
api-namevariable.This PR adds the definition of api-name to Common Vocabulary and Acronyms and clarifies the name of API definition files and servers object content
Which issue(s) this PR fixes:
Fixes #298 #284
Does this PR introduce a breaking change?
Special notes for reviewers:
Do we need similar definition of 'api-version'?
JSON format is not currently used in any subproject, should the file extension .json be removed?
Changelog input
Additional documentation