Jon Ursenbach
Jon Ursenbach
| 🚥 Resolves RM-8228 | | :------------------- | ## 🧰 Changes WIP work on a new `rebuild` command that will rebuild an existing installed API with the latest version or...
### Discussed in https://github.com/readmeio/api/discussions/545 Originally posted by **erunion** October 25, 2022 Because a lot of the work that `api` does behind the scenes can be a bit magical it'd be...
### Discussed in https://github.com/readmeio/api/discussions/544 Originally posted by **erunion** May 21, 2020 When working with an API, it's helpful to be able to mock out requests when unit testing client functionality....
https://swagger.io/docs/specification/describing-parameters/#common-parameters Currently common parameters are duplicated across path methods, resulting in a lot of duplicate lines of code in generated specifications. Migrate these up into common parameters and save a...
Like with the `TagReducer`, it would be nice to have the vendor tag and private/public resource visibility filtering code decoupled into a separate tool that you could supply a full...
 This changeset is technically a change because GET `/users/:user_id/tickets/:ticket` was previously returning a `204 No Content`, and now it returns a `200 OK` with a full representation. - [...
With the new MSON work in #42, the syntax for referencing another representation in a representation data is: ``` @api-data director (\Mill\Examples\Showtimes\Representations\Person) - Director ``` This is fine, but it's...
Currently we have no way to document that a resource action returns a collection of a type of response. For example, in the Vimeo API: ```json { "total": 66, "page":...
``` @api-return {collection} \App\Response\Response1|\App\Response\Response2 ``` When compiled into OpenAPI, this would probably have to be an `anyOf` representation instead of our standard `oneOf`.