Joseph Perez

Thanks for your quick response! I've added `RUN cat recipe.json` in the Dockerfile and here it is: ```json {"skeleton":{"manifests":[{"relative_path":"Cargo.toml","contents":"bench = []\ntest = []\nexample = []\n\n[[bin]]\npath = \"src/additional_binary.rs\"\nname = \"additional\"\ntest =...

> Data classes direct serialization is done by orjson like a charm. Actually, not really, because orjson only works with raw dataclasses and doesn't cover *apischema* features like [aliasing](https://wyfo.github.io/apischema/json_schema/#field-alias) (for...

I did not think about it when I was writing the issue, but the best solution could be to have simply `apischema.settings.serialization.type_checking = __debug__` by default. It would disable type...

> Because some wrong values can appear from a data source for many reasons. I think you misunderstood this issue. There is no question about deactivating type checking at deserialization....

> I really love this library for its simplicity and sticking as close to the stdlib dataclasses as possible. Thank you a lot for this feedback! Sticking to the stdlib...

Coming from FastAPI issue referenced above. @tomchristie I don't understand the issue about consuming the request in a middleware, could you explain this point ? In fact, I have the...

Is `@oneOf` missing in the example of section *Can this allow a field to accept both a scalar and an object?*

> **It’s not a directive** Why should it be something else than a directive? Actually, it's already (almost) possible to implement `@oneOf` as a directive in a few lines of...

@benjie In my previous comment, I've brought the fact that _oneof_ semantic could just be implemented as a directive by graphql libraries, without requiring the update of specifications. Could you...

Here is a POC of implementation, which could be directly integrated into *typing(_extensions)* ```python import sys from typing import * from typing import _collect_type_vars def _generic_mro(result, tp): origin = get_origin(tp)...