Update inconsistent --apiPath on Readme file #260
Merged
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
|
Thanks for your interest in palantir/conjure-postman, @MarcoLotz! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request. |
carterkozak
approved these changes
Aug 26, 2021
|
Thanks for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before this PR
The documentation is referencing a configuration --apiBase when the correct is --apiPath.
The source code of that configuration that confirms it can be found here:
https://github.com/palantir/conjure-postman/blob/f00b53fe4e5b11ba97579429c211ac7bdccd3711/conjure-postman/src/main/java/com/palantir/conjure/postman/cli/CliConfiguration.java
After this PR
==COMMIT_MSG==
updated documentation to be consistent with configuration implementation
==COMMIT_MSG==
Possible downsides?
No downsides.