Open db0 opened 8 months ago
This is going to require making sure the 'legacy' -> 'new' format parsing caries arbitrary fields across during the conversion process in production, but fails during testing (so they can be explicitly defined in pydantic basemodels).
I want to add a new key for models in the reference "optimization" which is optional, or "turbo", "lightning" etc