Francois LASNE

i come up with same requirement , spotting unused definition , and raising a warning could apply on definitions, and response for OAS this would enhance the swagger quality ....

😥 here we may miss the user experience , of the API designer as well as the Tooling implementer having enum with a value and a description is a definitive...

I agree this is a usefull feature (especially in EU with all the GDPR regulation) this would allows gateway , and logger to not take decision weither it should be...

I would rather go away of this and push any schema related feature to json schema rather than continue in forking json schema behaviour then not sure you may be...

given the subject is quite old , given a basic exemple has been provided in the merge request . Meaning you advertise that the API requires MutualTLS to be used...

@handrews looks it has been merged, it should be good ? or does the ticket kept open till version 3.2 is released ?

Same, confirming the issue is still there in version 6.8.0 is there update ? it s quite annoying as cannot see a simple workaround (i am unable to keep the...

i agree with @samgqroberts @frantuma , @char0n , @ponelat can you close this ticket for a cleanning reason (and also for project relying on this ticket to have a clearer...

i spend bunch of time to get the reason definitly your comment helps me a lot @ravage84 , So powerShell user : echo 'extends: ["spectral:oas"]' | Out-File .spectral.yaml -Encoding ascii

any news there ? @vadeg , @tkrop the issue you mentionned https://github.com/swagger-api/swagger-parser/issues/1535 looks fixed as statement below also here https://github.com/swagger-api/swagger-core/wiki/Swagger-2.X---OpenAPI-3.1 so we should be good here isn't it ?