This pullrequest adds them to the eve-swagger output.
Concerning testing: As I understand eve-swagger tests right now actually don't test all of openAPIs validity. I therefore just added the new schema keys into the test-settings.
(However, _id will still not be reported as readonly as it is a datarelation and openAPI does not support $ref and readOnly together. The fix for this in my fork is that I don't report the id as a relation, but this is probably not the perfect way to go)
the swagger 2.0 or openAPI specification also supports
readOnly
(which is evereadonly
) andpattern
(which is eve/cerberusregex
).This pullrequest adds them to the eve-swagger output.
Concerning testing: As I understand eve-swagger tests right now actually don't test all of openAPIs validity. I therefore just added the new schema keys into the test-settings.
(However,
_id
will still not be reported as readonly as it is a datarelation and openAPI does not support$ref
andreadOnly
together. The fix for this in my fork is that I don't report the id as a relation, but this is probably not the perfect way to go)