Adam Leventhal
Adam Leventhal
> * Why not simply use a `2XX` to exclude the other 200-series codes from `default`? The spec makes it clear that the `200` response would take precedence over `2XX`...
> In my opinion, the onus is on you to document the known responses. On the API description author... sure! I would merely observe that mistakes have occurred in the...
> > One could infer that 200 is the only success response, but what in the OpenAPI spec tells us that this is so? If default actually, de facto, is...
FYI I intend to make a concrete proposal year in January at the latest. Agreed that 3.1 support would be great. I'm increasingly convinced that relying on `schemars` is the...
This threw me for a loop as well trying to generate a Rust SDK based on the OpenAPI document. I would be happy to submit a PR that addresses this...
In addition to `Hash` I think you'd need `Eq` which can't be derived in particular because `NumberType` contains `f64`s that don't implement `Eq`. I'm planning on closing this in the...
I think that equality issues aren't limited to `NaN`s
I hit this today as well: input: ```rust impl Client { #[doc = "comment"] pub async fn key_changes_survey_response_education_organization_target_associations < 'a > (& 'a self , limit : Option < i64...
Updating this: Rain's suggestion for a macro to define these types was something along these lines: ```rust impl_typed_uuid_kind! { json_schema_settings = { crate = "my-crate", path = "my_crate", }; Collection...
So sorry I missed the gentle ping! Feel free to ping harder next time.