Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / mohsen1/multi-file-swagger-example issues and pull requests
#24 - Information on splitting definitions
Issue -
State: open - Opened by lauradP over 4 years ago
- 1 comment
#23 - Version 2.3.0 Not Resolving External File References Properly
Issue -
State: open - Opened by Machine-X- about 5 years ago
- 1 comment
#22 - Not working if folders are not in root
Issue -
State: closed - Opened by nassiharel over 5 years ago
- 2 comments
#21 - Updating dependencies which allows for nested reference resolution
Pull Request -
State: closed - Opened by ClaudioConsolmagno over 5 years ago
#20 - I want to break each PATH OPERATION into its own file
Issue -
State: open - Opened by ericweidl over 5 years ago
- 2 comments
#19 - Output files do include yarn console output
Issue -
State: closed - Opened by kopackiw almost 6 years ago
#18 - Unresolved local reference on resolved remote reference
Issue -
State: open - Opened by jcneves86 almost 6 years ago
- 1 comment
#17 - is there a way to break swagger down by tag routes ?
Issue -
State: open - Opened by NoSoup4you2 almost 6 years ago
#16 - remote references kept as is if there is no network connection
Issue -
State: open - Opened by dylan-colaco almost 7 years ago
#15 - Added option to output as yaml file
Pull Request -
State: closed - Opened by tanelso2 over 7 years ago
#14 - On NPM + Usable globally.
Pull Request -
State: closed - Opened by iain17 over 7 years ago
- 4 comments
#13 - Running into issue where my resolved JSON is not converted to correct YAML file.
Issue -
State: open - Opened by ngoctranfire almost 8 years ago
- 4 comments
#12 - Couldn't generate neither Server nor client
Issue -
State: closed - Opened by wal0x almost 8 years ago
- 1 comment
#11 - Cannot create property on string
Issue -
State: closed - Opened by falico about 8 years ago
- 2 comments
#10 - Where to put resolve.js in swagger generated structure
Issue -
State: closed - Opened by sandipwane about 8 years ago
- 2 comments
#9 - json: cannot unmarshal string into Go value of type spec.SchemaProps
Issue -
State: open - Opened by hagh over 8 years ago
- 3 comments
#8 - Document build/use instructions
Issue -
State: open - Opened by DALDEI almost 9 years ago
- 3 comments
Labels: question
#7 - Upgrade json-refs dependency - fixes #6
Pull Request -
State: closed - Opened by floydpink almost 9 years ago
- 1 comment
#6 - Current version of json-refs does not work with the existing code
Issue -
State: closed - Opened by floydpink almost 9 years ago
- 2 comments
#5 - Relative path to parent folder
Issue -
State: closed - Opened by floydpink almost 9 years ago
- 2 comments
#4 - Are we ought to use json-refs?
Issue -
State: open - Opened by PavelPolyakov almost 9 years ago
- 4 comments
#3 - Question on example / process workflow
Issue -
State: open - Opened by davisford almost 9 years ago
- 3 comments
#2 - post and get to same path gets swallowed
Issue -
State: closed - Opened by tobad357 about 9 years ago
- 1 comment
#1 - Definitions 'ref' is injected, not referenced
Issue -
State: closed - Opened by NadavK about 9 years ago
- 6 comments