Starting work on the v2 migration: api type generation, technologies and nodes partially working

silky commented 4 months ago

WIP on schema generation for v2 migration based on datamodel-code-generator.

Todo:

[x] Check that it's valid Python
[x] Check that it can be used to query the feo-core API
[x] Decide what functionality we want to support
[x] Implement it
[x] Test it
[ ] ~Set up a CI step to validate that the schema hasn't changed between the one we used and the one we want to deploy for~
[ ] ~Allow the dev to set the URL they want to query for the schema as an env var (FEO_API_URL seems useful)~
[x] Fix up all the pre-commit stuff post-generation
[x] Remove the date from the generated header (maybe?)
[ ] ~Check that there's no issue with geospatial types~

[ ] Dependencies install correctly in a clean environment and code executes;
[ ] Test coverage extended; created tests fail without the change (if possible);
[ ] All tests passing;
[ ] Commits follow a type convention (e.g. https://gist.github.com/brianclements/841ea7bffdb01346392c#type);
[ ] Extended the README, documentation and/or docstrings, if necessary;

vercel[bot] commented 4 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
feo-client	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2024 0:35am

notion-workspace[bot] commented 4 months ago

silky commented 3 months ago

closing as we will just use #142 once it's ready.

transition-zero / tz-client