search

Azure / openapi-diff

Command line tool to detect breaking changes between two openapi specifications
MIT License
266 stars 37 forks source link

Lint rule for adding new consumers #236

Closed tadelesh closed 2 years ago

tadelesh commented 2 years ago

From Jeffrey suggested, we need to add a lint rule for the situation: NEW response Content-Types always be added after OLD content types in the swagger. This could be result in breaking changes for SDK to generate multi operations for each content type and make one of the content type as default. If we could not get previous version info, we can only relay on the sequence user provided. So, it will be an easier way to limit user only add new consumer after the existed one.

jianyexi commented 2 years ago

@tadelesh if it's lint rule , please file issue via https://aka.ms/lintrulecandidate

tadelesh commented 2 years ago

Migrate to https://github.com/Azure/azure-openapi-validator/issues/371.