Support different filenames for API contracts #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @mkon,
what do you think about this feature that I've tried to implement?
I found your gem useful, but it would be great if it could use different filenames for contracts, instead of just
openapi.yaml
that was previously hard-coded, especially in cases where there are different versions of the API specs (contracts).For backward-compatibility reasons, I've set the default filename to
openapi.yaml
, but left the possibility for the user to define the name as a second argument.Hoping to hear your feedback and maybe contribute here.