Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / interagent/http-api-design issues and pull requests
#104 - Dead link in about section
Issue -
State: closed - Opened by holly-hacker 2 months ago
- 1 comment
#103 - add gitbook version translation fro simplfied chinese
Pull Request -
State: closed - Opened by ZhangBohan about 3 years ago
- 1 comment
#102 - uuid in doubt
Issue -
State: open - Opened by hujun8610 over 3 years ago
- 4 comments
#101 - Fix variable typo in standard response types section
Pull Request -
State: closed - Opened by santos22 almost 4 years ago
- 1 comment
#100 - Fix misspellings of 'delineation'
Pull Request -
State: closed - Opened by NateEag about 4 years ago
- 1 comment
#99 - Reworded
Pull Request -
State: closed - Opened by FrancescoGd over 4 years ago
- 2 comments
#97 - Links in README.md are 404 when viewed on Gitbook
Issue -
State: open - Opened by mxmlnglt almost 5 years ago
- 5 comments
#96 - Add guidance on providing standard response types
Pull Request -
State: closed - Opened by jessieay over 5 years ago
- 1 comment
#95 - Swaggerhub
Pull Request -
State: closed - Opened by ivan-novakov almost 6 years ago
- 3 comments
#94 - Json with PLSQL ( PLJSON)
Issue -
State: closed - Opened by flgarcia over 6 years ago
- 1 comment
#93 - The used time format is actually RFC5424, a subset of ISO8601
Issue -
State: open - Opened by ioggstream over 6 years ago
- 2 comments
#92 - Avoid partial records in relationships
Pull Request -
State: closed - Opened by caseywatts over 6 years ago
- 1 comment
#91 - Test Framework
Issue -
State: closed - Opened by martindale almost 8 years ago
- 1 comment
#90 - 200 and 201 and location headers
Pull Request -
State: closed - Opened by joe-mojo about 8 years ago
- 2 comments
#89 - add notes on collection actions
Pull Request -
State: open - Opened by geemus about 8 years ago
#88 - Add navigation links among EN pages
Pull Request -
State: closed - Opened by felipecao about 8 years ago
- 5 comments
#87 - Pagination using Range cannot be consistent
Issue -
State: closed - Opened by KellerFuchs over 8 years ago
- 8 comments
#86 - Fix Summary and Contributing links
Pull Request -
State: closed - Opened by benoittgt over 8 years ago
- 1 comment
#85 - updated italian translation
Pull Request -
State: closed - Opened by ghost over 8 years ago
- 2 comments
#84 - Italian translation for the http-api-design
Pull Request -
State: closed - Opened by ghost over 8 years ago
- 5 comments
#83 - readme typo
Pull Request -
State: closed - Opened by mtavano almost 9 years ago
- 2 comments
#82 - broken link to section on ranges
Pull Request -
State: closed - Opened by OscarScholten almost 9 years ago
- 2 comments
#81 - Paginating/ranging over non-unique fields
Issue -
State: open - Opened by bjeanes about 9 years ago
- 15 comments
#80 - Current version of the API, new v2
Pull Request -
State: closed - Opened by openmosix about 9 years ago
- 2 comments
#79 - Why use UUID?
Issue -
State: closed - Opened by rafaelrabeloit about 9 years ago
- 12 comments
#78 - Add Portuguese version link
Pull Request -
State: closed - Opened by Gutem about 9 years ago
- 1 comment
#77 - No more etags
Pull Request -
State: closed - Opened by openmosix about 9 years ago
#76 - Move bullets from Requests to Responses
Pull Request -
State: closed - Opened by ms-ati over 9 years ago
- 2 comments
#75 - Consider compatibility with jsonapi.org?
Issue -
State: open - Opened by ms-ati over 9 years ago
- 8 comments
#74 - added turkish translation link
Pull Request -
State: closed - Opened by hkulekci over 9 years ago
- 3 comments
#73 - Add Spanish translation
Pull Request -
State: closed - Opened by jmnavarro over 9 years ago
- 1 comment
#72 - detail expansions
Issue -
State: open - Opened by geemus over 9 years ago
#71 - Fix typo
Pull Request -
State: closed - Opened by DyegoCosta over 9 years ago
- 2 comments
#70 - include more examples for main points
Issue -
State: open - Opened by geemus over 9 years ago
- 9 comments
#69 - consider expanding error messaging as per white house guide
Issue -
State: open - Opened by geemus over 9 years ago
- 7 comments
#68 - Consider adding language specific resources for implementing these principles
Issue -
State: open - Opened by gooddadmike over 9 years ago
- 1 comment
#67 - add "Translations"
Pull Request -
State: closed - Opened by kcyeu over 9 years ago
- 1 comment
#66 - Traditional Chinese version, and add "List of Translations"
Issue -
State: open - Opened by kcyeu over 9 years ago
- 5 comments
#65 - Add a missing dot
Pull Request -
State: closed - Opened by chentsulin over 9 years ago
- 1 comment
#64 - replace broken link #paginate-with-ranges
Pull Request -
State: closed - Opened by chentsulin over 9 years ago
- 1 comment
#63 - fix Accept header typo
Pull Request -
State: closed - Opened by dpassage over 9 years ago
- 1 comment
#62 - Create a website (Gitpage)
Issue -
State: closed - Opened by weblancaster over 9 years ago
- 3 comments
#61 - Using 409 Conflict for uniqueness checks
Issue -
State: open - Opened by schatekar over 9 years ago
- 2 comments
#60 - How are you modeling authentication operation?
Issue -
State: open - Opened by schatekar almost 10 years ago
- 1 comment
#59 - I'm curious to know the reasoning for going with JSON Schemas instead of Swagger
Issue -
State: closed - Opened by c4milo almost 10 years ago
- 5 comments
#58 - Guidance on implementing REST interfaces for state machine
Issue -
State: open - Opened by schatekar almost 10 years ago
- 21 comments
#57 - Dealing With "ChoiceFields"
Issue -
State: open - Opened by cooncesean almost 10 years ago
- 9 comments
#56 - Guidance about what is properly part of a resource
Issue -
State: open - Opened by tomrogers42 almost 10 years ago
- 7 comments
#56 - Guidance about what is properly part of a resource
Issue -
State: open - Opened by tomrogers42 almost 10 years ago
- 7 comments
#55 - Added use of HTTP 400 Bad Request for failed validation on request body content
Pull Request -
State: closed - Opened by schatekar almost 10 years ago
- 5 comments
#54 - Mention PUT in suggested response status codes
Pull Request -
State: closed - Opened by krallin almost 10 years ago
- 4 comments
#53 - Explain every paragraph
Issue -
State: open - Opened by ksimka almost 10 years ago
- 4 comments
#52 - Paginated search results
Issue -
State: closed - Opened by glenscott almost 10 years ago
- 3 comments
#51 - Code block color changes and removed extra space in minification example.
Pull Request -
State: closed - Opened by eerwitt almost 10 years ago
- 1 comment
#50 - Replace HTTP/1.1 RFC 2616 reference with RFC 7231.
Pull Request -
State: closed - Opened by triplepoint almost 10 years ago
- 1 comment
#49 - minimize path-nesting
Issue -
State: open - Opened by geemus almost 10 years ago
- 4 comments
#48 - Fixes #45 Changing "Require TLS" section
Pull Request -
State: closed - Opened by elmariofredo about 10 years ago
- 3 comments
#47 - Why have version in headers and not URLs?
Issue -
State: open - Opened by sujaymansingh about 10 years ago
- 4 comments
#46 - Guidance on JSON escaping for non-ascii characters.
Issue -
State: closed - Opened by tomchristie about 10 years ago
- 11 comments
#45 - Why redirects make TLS useless and 403 can protect it?
Issue -
State: closed - Opened by crabhit about 10 years ago
- 10 comments
#44 - Link properly to 'Keep JSON minified' in contents.
Pull Request -
State: closed - Opened by tomchristie about 10 years ago
- 1 comment
#43 - Remove recommendation to prettify JSON
Pull Request -
State: closed - Opened by keithamus about 10 years ago
- 1 comment
#42 - Recommend JSON to be minified
Pull Request -
State: closed - Opened by keithamus about 10 years ago
- 1 comment
#41 - Recommend synchronous DELETE requests return 204
Pull Request -
State: open - Opened by keithamus about 10 years ago
- 3 comments
#40 - Recommend `indent` option for Pretty-Printing JSON
Pull Request -
State: closed - Opened by keithamus about 10 years ago
- 27 comments
#39 - Better example for the Resource Names
Issue -
State: closed - Opened by keithamus about 10 years ago
- 10 comments
#38 - s/Request-Id/X-Request-Id
Pull Request -
State: closed - Opened by keithamus about 10 years ago
- 1 comment
#37 - Responding for non-TLS requests
Pull Request -
State: closed - Opened by rhoberman about 10 years ago
- 3 comments
#36 - Further explanation of the Range header for pagination
Issue -
State: open - Opened by gulopine about 10 years ago
- 42 comments
#35 - note down differences in PUT, POST and PATCH
Issue -
State: open - Opened by rstacruz about 10 years ago
- 5 comments
#34 - Suggest error codes
Issue -
State: closed - Opened by rstacruz about 10 years ago
- 5 comments
#33 - ? semantic hinting
Issue -
State: open - Opened by geemus about 10 years ago
- 20 comments
#32 - consider just having gh-pages version?
Issue -
State: closed - Opened by geemus about 10 years ago
- 2 comments
#31 - adding github pages
Pull Request -
State: closed - Opened by karlcoelho about 10 years ago
- 4 comments
#30 - Should authorization and authentication error codes be pointed out?
Pull Request -
State: closed - Opened by steookk about 10 years ago
- 1 comment
#29 - Contents are easier to read if divided in sections
Pull Request -
State: closed - Opened by steookk about 10 years ago
- 2 comments
#28 - added 'minimize path nesting' in Contents
Pull Request -
State: closed - Opened by steookk about 10 years ago
- 1 comment
#27 - Korean version of the guidelines
Pull Request -
State: closed - Opened by yoondo about 10 years ago
- 9 comments
#26 - the guide in Github Pages?
Issue -
State: closed - Opened by karlcoelho about 10 years ago
- 4 comments
#25 - Thoughts on authentication
Issue -
State: open - Opened by rudolphfroger over 10 years ago
- 11 comments
#24 - Wrap collection responses in a hash
Pull Request -
State: closed - Opened by andyw8 over 10 years ago
- 8 comments
#23 - s/SSL/TLS/
Pull Request -
State: closed - Opened by iffy over 10 years ago
- 1 comment
#22 - Should "SSL" be replaced with "TLS"?
Pull Request -
State: closed - Opened by travispaul over 10 years ago
- 2 comments
#21 - Description about REST security and session handling with JWT (JSON Web Token)
Issue -
State: closed - Opened by patoi over 10 years ago
- 3 comments
#20 - remove quotes from "service_class"
Pull Request -
State: closed - Opened by jamesmanning over 10 years ago
- 1 comment
#19 - expand request-limiting guide to allow programmatic behavior response to rate limiting
Issue -
State: open - Opened by jamesmanning over 10 years ago
- 6 comments
#18 - Shouldn't JSON properties be camelCase?
Issue -
State: closed - Opened by aronwoost over 10 years ago
- 10 comments
#17 - thoughts on how to perform actions on resources
Issue -
State: closed - Opened by neonstalwart over 10 years ago
- 5 comments
#16 - POST should not always return 201
Pull Request -
State: closed - Opened by joe-mojo over 10 years ago
- 15 comments
#15 - Why no 204?
Issue -
State: open - Opened by rikvanmechelen over 10 years ago
- 12 comments
#14 - 12333
Issue -
State: closed - Opened by teachar over 10 years ago
#13 - Outline what happens on well formed but invalid data
Issue -
State: open - Opened by ransombriggs over 10 years ago
- 4 comments
#12 - Nest Foreign Key Relations
Issue -
State: open - Opened by nateklaiber over 10 years ago
- 1 comment
#11 - Update README.md
Pull Request -
State: closed - Opened by neonstalwart over 10 years ago
- 1 comment
#10 - fix UTC time named anchor
Pull Request -
State: closed - Opened by snkashis over 10 years ago
- 1 comment
#9 - Explain why to prefer "full resource when available"
Issue -
State: open - Opened by geemus over 10 years ago
- 7 comments
#8 - Explain why to version in accept header
Issue -
State: open - Opened by justincy over 10 years ago
- 15 comments
#7 - Human spell check
Pull Request -
State: closed - Opened by stevenbeeckman over 10 years ago
- 1 comment
#6 - Remove erroneous reference to JSON property names.
Pull Request -
State: closed - Opened by couchand over 10 years ago
- 2 comments
#5 - Disagreement with the explanation of 202 Status Code
Issue -
State: closed - Opened by harikt over 10 years ago
- 2 comments