[nancyfx] Issue #5196: make package GUID nonrandom for nancyfx samples#5209
Merged
wing328 merged 2 commits intoswagger-api:masterfrom Mar 27, 2017
Conversation
ePaul
changed the title
spr3nk3ls
pushed a commit
to spr3nk3ls/swagger-codegen
that referenced
this pull request
Mar 28, 2017
…cyfx samples (swagger-api#5209) * Add packageGuid parameter to NancyFxServerCodegen. * Use packageGuid parameter for nancyfx petstore samples.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR checklist
./bin/to update Petstore sample so that CIs can verify the change.→ bin/nancyfx-petstore-server.sh
Description of the PR
This adds a
packageGuidparameter to NancyFXServerCodegen, which allows to pass a fixed GUID, instead of a randomly generated one.The petstore sample generation script then uses this option (with the last random value from master) to generate the samples. This way there are no random changes between sample updates which obscured the real changes. (This is a part of #5196.)