Matthew Evans

> Turns out the custom BaseModel was adding some stuff to 'extra' in FieldInfo that it was using for its own internals. Now that `extra` is defaulted to `allow` those...

Right, I'm with you now. > The only valid extra kwargs that `Field()` could possibly take without breaking the spec validator is those that begin with `x-`, although you cannot...

Just tested again and this bug is still affecting v0.75.1. It would be great to get some confirmation that a fix to FastAPI would be useful, perhaps following @mreschke's workaround...

Is there any chance you could confirm this is a bug @tiangolo, 1 year on? If not, I am happy to prepare a docs PR that tries to explain the...

> Any progress on this one? I made a pull request to the docs warning people about this (#4846) but it hasn't gotten any traction either, I wonder if anyone...

Thanks for breaking it down @tiangolo!

Here's the slightly kludgey way we got around it @trondhindenes, in case it is useful to you: https://github.com/Materials-Consortia/optimade-python-tools/pull/1131/files Basically: - stop using `const` and use a `regex` that matches the...

Hope this is the correct place to comment, but I would suggest adding an OPTIMADE API client, which is supported by the databases listed above. We just release an asynchronous...

You may not need this anymore, but you can use `tlmgr` within the container to install any extra texlive packages you need. You can either do this for every build...

> On line 655 there is still an example of a response. I think your database field should be added to this example. Not sure it's super important, as `database`...