Jon Ursenbach

There is currently no way to document that a scope is now required on a new API version.

#### \Api\Response\VideoResponse ``` /** * @api-data play (\Api\Response\PlayResponse, CAPABILITY_PLAY_REPRESENTATION) - Play representation * @api-version >=3.3 * @api-see \Api\Response\PlayResponse::_json play */ ``` #### \Api\Response\PlayResponse ``` /** * @api-data dash (\Api\Response\VideoFileHlsDashResponse) -...

With the new MSON work being done in [mill#42](https://github.com/vimeo/mill/issues/42), the current parameter token system is no longer viable. The way it was originally constructed was that it would `str_replace` content...

> Can we make the field names in the description yellow like the body (eg in "Deprecated metadata.connections.activities in the User representation" metadata.connections.activities should be yellow) We should add in...

Better deprecation support

1

*This is partly related to https://github.com/vimeo/mill/issues/21.* Right now, the Mill `deprecated` annotation decorator makes it awful to document why something was deprecated. There is also no way to designate that...

Adding support for `.example()` to document schema examples

10

I've added a new `.example()` method that, like `.describe()`, will allow consumers to document example values and representations of their schemas. ```ts const documentedString = z .string() .url() .example("https://example.com") .example("https://example.local");...