Jon Ursenbach

`@api-return` and `@api-throws` are getting a new MSON-like syntax with this change: Old: > @api-return:public {object} \Mill\Examples\Showtimes\Representations\Theater > @api-throws:public {404} \Mill\Examples\Showtimes\Representations\Error If the movie could not be found. > @api-throws:public...

I think there are a few options we can do: * Add a `methods` attribute to the `` element for controllers in `mill.xml`, that takes a comma separated list of...

Another option we can do is support regex on `methods` annotations. So if you don't support `GET`, `PATCH`, etc. but at least have a common format for your controller methods,...

Along with the config change necessary to handle this, we'll also need to update the `@api-uri` annotation to support supplying an HTTP method, since that method will no longer be...

The new plan is to introduce an `@api-method` annotation that'll solve all of these problems automatically.

Another common example of this is enum values differing between API versions: ``` * @api-param:public {filter} * + Members * - `embeddable` * - `playable` * - `app_only` * *...

Trying to do the above example with enum reductions isn't going to work. Maybe the best bet is just to force the developer to copy documentation from one version to...

We also can't say **when** something was deprecated.

We originally had an `@api-deprecated` annotation, but ended up moving that to be a special "decorator" for URI's and parameters only (eg. `@api-uri:public:deprecated`). I think the best thing to do...

Nobody at Vimeo has touched this repo since I left in March, and I don't have permissions either to do this. :(