Support the --port option #81
Draft
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
BREAKING CHANGE: It is now required that the hooks handler process is able to accept a --port option in addition to the list of hook files.
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.
This is a kick off to address the long-pending #11 and #17. Big thanks to @ddelnano for contributing the initial work and opening the discussion back in the days. I'm sorry this is taking so long to tackle, but as you can see in apiaryio/dredd#917, it got stuck on various circular chicken-egg dependency issues.
Closes #11, closes #17
BREAKING CHANGE: After this PR gets merged, it is going to be required that the hooks handler process is able to accept a
--portoption in addition to the list of hook files.