-
Depends on #883
Design and implement support for generating partially-expanded link templates given an action. Consider exposing in RFC-6570 format.
Needs to be broken down further once we have desi…
-
If an ID is a string, and the string ID has a comma, how should the id string be represented in a comma-separated list of ids (e.g. in a URL request `/comments?ids=5,12,17,20`)? Or should this be expr…
-
I noticed the API demo at https://ohana-api-demo.herokuapp.com/api returns this:
```
{
organizations_url: "https://ohana-api-demo.herokuapp.com/api/organizations{/organization_id}",
locations_url: "h…
-
Is this supposed to be supported?
Currently 'trying' an operation with where path parameters are not defined results in the entire sub path being omitted from the request
e.g a call to `GET /users/{i…
-
Falls Parameter übergeben werden, dann können dafür _URI Templates_ gemäß RFC 6570 verwendet werden (http://tools.ietf.org/html/rfc6570).
Aktuell ist dies möglicherweise für diese Issues relevant: #1…
-
There are real APIs where a query string may determine the structure of the response, for example `verbose=true`, `metadata=1`, `action=reboot`.
However, Those cannot be expressed in Swagger 2.0 toda…
-
Would it be possible to support "{}" for named parameters. This is according to http://tools.ietf.org/html/rfc6570 May be configurable so that one can use ":" or {}.
-
Referencing PR #237 as a few minutes ago it is not possible to link from resources which have internal structure, eg:
```
{
"data": {
"eab9b2af-73f0-4e13-b348-0bd4377fb06a": {
"type": "co…
-
I would suggest Pux to add support for RFC 6570 which is a comprehensive way for URI templating.
Here's a PHP extension implementation: https://github.com/ioseb/uri-template
And here's the RFC: http…
-
It seems that right now we have several ways of representing resources, and some discussion about this (https://github.com/json-api/json-api/issues/275, https://github.com/json-api/json-api/issues/268…