Phil Sturgeon
Phil Sturgeon
Seeing as format is by default merely an annotation it may not be used at all in the validaiton process. In order to keep things secure, if you're using OpenAPI-based...
Sorry, semantic release is bugging out, I'm trying to figure out why and get a proper version out now.
It's been released now, but I'm getting errors trying to use it. ``` spectral lint openapi.yaml --verbose Found 84 rules (73 enabled) Linting /Users/phil/src/bump/train-travel-api/openapi.yaml Error running Spectral! Error #1: scope.sandbox.value.match...
@StefanLecho can you upgrade, are you also getting this?
2.0.1 resolved this error. You can close the issue.
It's pretty handy for the client to know how long the data is going to be so they're not getting screwed up trying to bung it all into a field...
@DavidBiesack I'd be interested in your thoughts on this, as the default behavior for additional properties has changed in OAS 3.1 to make it more permissive. The rules you wrote...
JSON Schema has always allowed additional properties by default, that hasn't changed. What did change in OpenAPI v3.1 was `schema` becoming a proper JSON Schema Vocabulary instead of something vaguely...
@DavidBiesack > That 3.0.3 vs. 3.1.0 language is not talking about the JSON schema additionalProperties keyword (i.e. whether a JSON value can have properties not listed in the schema properties)...
I don't have enough context to know if variable names should be case sensitive or not, I don't think it matters too much either way? Some people will expect it...