Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / luckymarmot/paw-swaggerimporter issues and pull requests
#41 - No tags when importing from Swagger
Issue -
State: open - Opened by pildit almost 4 years ago
#40 - Import Failed: because of "- {}" in yaml file
Issue -
State: open - Opened by bindermuehle almost 5 years ago
#39 - Support Open API 3.0
Issue -
State: open - Opened by baseten over 6 years ago
- 31 comments
#38 - TypeError: Parameter 'url' must be a string, not object
Issue -
State: open - Opened by drallgood about 7 years ago
- 22 comments
#37 - Feature request: Import from swagger-ui spec
Issue -
State: open - Opened by josser over 7 years ago
- 3 comments
#36 - Makefile missing
Issue -
State: open - Opened by databus23 over 7 years ago
#35 - schema reference not expanded for request body
Issue -
State: open - Opened by databus23 over 7 years ago
- 5 comments
#34 - apiKey securityDefinition is not respecting header key
Issue -
State: closed - Opened by databus23 over 7 years ago
- 3 comments
#33 - Failed to correctly import swagger yml file due to Content-Type error
Issue -
State: closed - Opened by amelnikov-mylivn over 7 years ago
- 1 comment
#32 - Import failed - undefined is not an object
Issue -
State: closed - Opened by lumaxis over 7 years ago
- 9 comments
#31 - Import failing
Issue -
State: open - Opened by wimleers over 7 years ago
- 3 comments
#30 - Import not working
Issue -
State: closed - Opened by drct almost 8 years ago
- 2 comments
Labels: bug
#29 - Import not working
Issue -
State: closed - Opened by magobaol about 8 years ago
- 19 comments
Labels: OS:Yosemite
#29 - Import not working
Issue -
State: closed - Opened by magobaol about 8 years ago
- 19 comments
Labels: OS:Yosemite
#28 - Body parameters?
Issue -
State: closed - Opened by mwickens about 8 years ago
- 10 comments
#27 - cannot export when using environment variables
Issue -
State: closed - Opened by ridvanbaluyos about 8 years ago
- 6 comments
#27 - cannot export when using environment variables
Issue -
State: closed - Opened by ridvanbaluyos about 8 years ago
- 6 comments
#26 - Support importing host and schemes attributes as environment variables
Issue -
State: closed - Opened by lumaxis about 8 years ago
- 4 comments
Labels: enhancement
#25 - Does not correctly handle multiple "schemes" values
Issue -
State: closed - Opened by lumaxis over 8 years ago
- 6 comments
#25 - Does not correctly handle multiple "schemes" values
Issue -
State: closed - Opened by lumaxis over 8 years ago
- 6 comments
#24 - definition references not correctly parsed
Issue -
State: closed - Opened by klh over 8 years ago
- 5 comments
Labels: question
#24 - definition references not correctly parsed
Issue -
State: closed - Opened by klh over 8 years ago
- 5 comments
Labels: question
#23 - fixed travis
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
#23 - fixed travis
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
#22 - TypeError: undefined is not a function
Issue -
State: closed - Opened by lorengreenfield over 8 years ago
- 4 comments
#22 - TypeError: undefined is not a function
Issue -
State: closed - Opened by lorengreenfield over 8 years ago
- 4 comments
#21 - Show example in body
Issue -
State: closed - Opened by bertramakers over 8 years ago
- 8 comments
#21 - Show example in body
Issue -
State: closed - Opened by bertramakers over 8 years ago
- 8 comments
#20 - Importer fails on ValidationError
Issue -
State: closed - Opened by peterdewinter over 8 years ago
- 9 comments
#19 - 018 multiple context support
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
- 1 comment
#19 - 018 multiple context support
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
- 1 comment
#18 - Ignore broken schemas
Issue -
State: closed - Opened by mittsh over 8 years ago
- 1 comment
#18 - Ignore broken schemas
Issue -
State: closed - Opened by mittsh over 8 years ago
- 1 comment
#17 - starting the migration -- high chances of breaking
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
Labels: enhancement
#17 - starting the migration -- high chances of breaking
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
Labels: enhancement
#16 - Adapt to use the new import API
Pull Request -
State: closed - Opened by mittsh over 8 years ago
- 2 comments
#16 - Adapt to use the new import API
Pull Request -
State: closed - Opened by mittsh over 8 years ago
- 2 comments
#15 - bumped version to correct number. removed .nvmrc from gitignore
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
#15 - bumped version to correct number. removed .nvmrc from gitignore
Pull Request -
State: closed - Opened by JonathanMontane over 8 years ago
#14 - Globally configured 'consumes' attribute will be propagated down to individual requests
Pull Request -
State: closed - Opened by egbertp over 8 years ago
- 1 comment
#14 - Globally configured 'consumes' attribute will be propagated down to individual requests
Pull Request -
State: closed - Opened by egbertp over 8 years ago
- 1 comment
#13 - grouping requests by resource name (first path segment)
Pull Request -
State: closed - Opened by nosyjoe over 8 years ago
- 3 comments
#13 - grouping requests by resource name (first path segment)
Pull Request -
State: closed - Opened by nosyjoe over 8 years ago
- 3 comments
#12 - Feature Request: Group by Path
Issue -
State: closed - Opened by letsbyteit over 8 years ago
- 15 comments
#12 - Feature Request: Group by Path
Issue -
State: closed - Opened by letsbyteit over 8 years ago
- 15 comments
#11 - Use default values for parameter values instead of their names
Pull Request -
State: closed - Opened by nosyjoe almost 9 years ago
- 2 comments
#11 - Use default values for parameter values instead of their names
Pull Request -
State: closed - Opened by nosyjoe almost 9 years ago
- 2 comments
#10 - support string parameters with possible values as enum
Issue -
State: closed - Opened by nosyjoe almost 9 years ago
- 7 comments
#10 - support string parameters with possible values as enum
Issue -
State: closed - Opened by nosyjoe almost 9 years ago
- 7 comments
#9 - URL Import
Issue -
State: closed - Opened by nVitius almost 9 years ago
- 5 comments
#9 - URL Import
Issue -
State: closed - Opened by nVitius almost 9 years ago
- 5 comments
#8 - improve env created with baseURL
Pull Request -
State: closed - Opened by hoegertn about 9 years ago
- 2 comments
#8 - improve env created with baseURL
Pull Request -
State: closed - Opened by hoegertn about 9 years ago
- 2 comments
#7 - Import host information as environment
Issue -
State: closed - Opened by hoegertn about 9 years ago
- 4 comments
#7 - Import host information as environment
Issue -
State: closed - Opened by hoegertn about 9 years ago
- 4 comments
#6 - Import fails with swagger.json
Issue -
State: closed - Opened by hoegertn about 9 years ago
- 8 comments
#6 - Import fails with swagger.json
Issue -
State: closed - Opened by hoegertn about 9 years ago
- 8 comments
#5 - Can you support Grape Swagger ?
Issue -
State: open - Opened by 42thcoder about 9 years ago
- 4 comments
#5 - Can you support Grape Swagger ?
Issue -
State: open - Opened by 42thcoder about 9 years ago
- 4 comments
#4 - Multifile-import
Issue -
State: closed - Opened by tuexss about 9 years ago
- 8 comments
#3 - Option doesn't show up in importable file types list
Issue -
State: closed - Opened by govyrl about 9 years ago
- 3 comments
#3 - Option doesn't show up in importable file types list
Issue -
State: closed - Opened by govyrl about 9 years ago
- 3 comments
#2 - root basepath
Issue -
State: closed - Opened by tuexss about 9 years ago
- 3 comments
#1 - when "produces":["application/json;charset=UTF-8"] , it will import fails
Issue -
State: closed - Opened by chenxiaolei over 9 years ago
- 2 comments
#1 - when "produces":["application/json;charset=UTF-8"] , it will import fails
Issue -
State: closed - Opened by chenxiaolei over 9 years ago
- 2 comments