You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
Adding an new "requires" validation parameter could be useful when validation queries. I would like to suggest the syntax requires: path for specifying that a parameter requires another for use. For example:
queryParameters:
lat:
type: stringrequires: lnglng:
type: stringrequires: lat
The text was updated successfully, but these errors were encountered:
At least i'm looking for a way to avoid having statements like "don't use with parameter xy..." in a description. For the example of Oauth2, maybe a smart conflicts property could capture conflicts when a certain named parameter is set to a specific value, i.e. conflicts: { namedParameter: "conflictsIfNamedParameterHasThisValue"}
@blakeembrey Regarding the lat/lon example - there's a simple alternative to it, namely requiring a combined parameter. I've see that in the google elevation api (?locations=64.330000,7.500000), and in the api i'm currently building we simply refer to the geouri formatting rules defined in RFC5870 - which is effectively the same plus optional altitude and uncertainty values.
Adding an new "requires" validation parameter could be useful when validation queries. I would like to suggest the syntax
requires: path
for specifying that a parameter requires another for use. For example:The text was updated successfully, but these errors were encountered: