Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / buildo/metarpheus-js-http-api issues and pull requests
#29 - no way to add parsers without redefining default ones
Issue -
State: open - Opened by veej almost 7 years ago
#28 - nice to have: pass data={} in case of POST with no body params
Issue -
State: open - Opened by giogonzo almost 7 years ago
#27 - #26: handle routeParamType shape change from https://github.com/buildo/metarpheus-tcomb/pull/25 (closes #26)
Pull Request -
State: closed - Opened by francescogior about 7 years ago
- 1 comment
Labels: breaking
#26 - handle routeParamType shape change from https://github.com/buildo/metarpheus-tcomb/pull/25
Issue -
State: closed - Opened by francescogior about 7 years ago
Labels: breaking
#25 - #24: Use scriptoni for linting (closes #24)
Pull Request -
State: closed - Opened by veej over 7 years ago
- 1 comment
#24 - Use scriptoni for linting
Issue -
State: closed - Opened by veej over 7 years ago
#23 - #22: `npm test` hangs (closes #22)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
Labels: bug
#22 - `npm test` hangs
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: bug
#21 - #20: fix body type check (closes #20)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
#20 - avoid false positive with Structs as body type
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: bug
#19 - #18: warn when passing data (body) to an api but no metarpheus typing is available for it (closes #18)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
Labels: in review
#18 - warn when passing data (body) to an api but no metarpheus typing is available for it
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: in review
#17 - #16: js-minifier-friendly envify (closes #16)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
Labels: defect
#16 - js-minifier-friendly envify
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: defect
#15 - #14: typecheck request body (closes #14)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
#14 - typecheck request body
Issue -
State: closed - Opened by giogonzo over 7 years ago
#13 - #12: be sure to reject if error response parsing fails (closes #12)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
Labels: bug, in review
#12 - be sure to reject if error response parsing fails
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: bug
#11 - Be sure to always reject if anything in the response chain fails
Issue -
State: open - Opened by giogonzo over 7 years ago
Labels: bug
#10 - #2: default `parseError` fn doesn't work (closes #2)
Pull Request -
State: closed - Opened by veej over 7 years ago
- 1 comment
Labels: bug, in review
#9 - warn if api responds with non-gzipped content
Issue -
State: open - Opened by giogonzo over 7 years ago
#8 - #7: `parser.test` should just return a boolean (closes #7)
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
Labels: defect, in review
#7 - `parser.test` should just return a boolean
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: defect
#6 - do we need/use the `.fromAPI` convention?
Issue -
State: open - Opened by giogonzo over 7 years ago
Labels: defect
#5 - passing api responses through `returnType`
Issue -
State: open - Opened by giogonzo over 7 years ago
Labels: defect
#4 - content-type: application/json
Issue -
State: open - Opened by giogonzo over 7 years ago
Labels: defect
#3 - do we need to `stringifyParams`?
Issue -
State: open - Opened by giogonzo over 7 years ago
Labels: defect
#2 - default `parseError` fn doesn't work
Issue -
State: closed - Opened by giogonzo over 7 years ago
Labels: bug
#1 - Create README.md
Pull Request -
State: closed - Opened by giogonzo over 7 years ago
- 1 comment
Labels: WIP