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
using petstore.yaml
and the "required_param_has_default": "error" config option
adding default: some_stringhere on a parameter and running lint-openapi does correctly return an error
however setting default: some_stringhere on a property does not return a error
the config option "required_param_has_default": "error" refers to param so I guess this excludes request body objects etc (?)
if so, I was wondering if this is something that makes sense to add (because it seems equally incorrect on a param and request body object's prop)?
(I'm using version 0.51.3)
The text was updated successfully, but these errors were encountered:
@sebas-intellegens Apologies for the late reply here. That's certainly worth considering, though we currently have a suite of higher-priority rules we're implementing and don't have much extra bandwidth. If this is important for your use case in the short term, I recommend extending our ruleset with a custom rule that enables this enforcement.
using petstore.yaml
and the
"required_param_has_default": "error"
config optionadding
default: some_string
here on a parameter and runninglint-openapi
does correctly return an errorhowever setting
default: some_string
here on a property does not return a errorthe config option
"required_param_has_default": "error"
refers toparam
so I guess this excludes request body objects etc (?)if so, I was wondering if this is something that makes sense to add (because it seems equally incorrect on a param and request body object's prop)?
(I'm using version
0.51.3
)The text was updated successfully, but these errors were encountered: