-
Notifications
You must be signed in to change notification settings - Fork 43
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
feat(openapi): version handling improvements #559
Merged
kanadgupta
merged 22 commits into
main
from
kanad/rm-4984-if-run-in-ci-environment-just-assume
Aug 10, 2022
Merged
feat(openapi): version handling improvements #559
kanadgupta
merged 22 commits into
main
from
kanad/rm-4984-if-run-in-ci-environment-just-assume
Aug 10, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This test broke because we slightly refactored the order in which we do version selection, so it had a nock that is no longer being hit.
kanadgupta
added
enhancement
New feature or request
refactor
Issues about tackling technical debt
command:docs
Issues pertaining to the `docs`, `changelogs`, or `custompages` commands
command:openapi
Issues pertaining to the `openapi`, `validate`, `reduce`, or `swagger` commands
command:categories
Issues pertaining to the `categories` commands
labels
Aug 8, 2022
Just as an additional sanity check, gonna use the weird version file again so we can ensure its version is not being adhered to unless the corresponding flag is passed.
kanadgupta
requested review from
a team,
erunion and
Dashron
and removed request for
a team
August 8, 2022 23:50
this should have been a separate PR lol sorry
wtf VSCode...
erunion
approved these changes
Aug 9, 2022
Co-Authored-By: Jon Ursenbach <[email protected]>
kanadgupta
deleted the
kanad/rm-4984-if-run-in-ci-environment-just-assume
branch
August 10, 2022 05:39
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
command:categories
Issues pertaining to the `categories` commands
command:docs
Issues pertaining to the `docs`, `changelogs`, or `custompages` commands
command:openapi
Issues pertaining to the `openapi`, `validate`, `reduce`, or `swagger` commands
enhancement
New feature or request
refactor
Issues about tackling technical debt
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.
🧰 Changes
openapi
,docs
, andcategories
commands). When the user fails to pass a--version
parameter in a CI environment, we just default to the main version (and inform the user of this via a warning—see below)--useSpecVersion
parameter to theopenapi
command that uses the version in theinfo.version
field of the spec for the ReadMe project version--version
parameter description into a separate file calledsrc/lib/versionOpt.js
where it was appropriate to do soinfo
statements🧬 QA & Testing
I added test coverage for all this new version-handling logic. Alternatively, you can checkout this branch and run the following command to confirm that the command will try to sync to
v1.2.3
of your project: