Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OpenAPI Diff to compare two OpenAPI specification files #546

Open
wants to merge 5 commits into
base: dev
Choose a base branch
from

Conversation

fabich
Copy link

@fabich fabich commented Feb 1, 2021

Hi @darrelmiller

A long long time ago we had a quick talk about a tool to compare two OpenAPI specification files.
I finally got the time to open a PR.

Please let me know what you think!

Best regards

fabich

Fabian Niederer and others added 4 commits February 1, 2021 17:55
@fabich
Copy link
Author

fabich commented Feb 17, 2021

we open-sourced this code in another repo until this PR can be merged.
https://github.com/LimeFlight/openapi-diff.

@darrelmiller
Copy link
Member

Hey @fabich thanks for the PR. We currently have three different implementations of OpenAPI diff capabilities and they all take a different approach. I'm thinking that the best option is to have each implementation get distributed as a different package so that people can choose the solution that works for them. I have failed to find the time to do the work that is needed to incorporate diff into the main library and I think I need to stop trying. I'm going to remove the partial implementation of the comparers that are in the vNext branch. Maybe we will pick that up later and expose as it's own package.

@Anakael
Copy link

Anakael commented Feb 27, 2023

I've just started creating one more tool there: :)
https://github.com/Anakael/OpenApiChecker
It's just MVP for now, but it is able to compare not old/new specs, but generated with requried ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants