Javier Ríos
Javier Ríos
We should be able to launch a data ingest job from our website with a subset of configuration (e.g. `graphql` factory with fields we know won't change in the refactor)....
Instead of saving the first image as the image preview for our notebooks, we could scan all of them and show a dropdown so that the user selects which plot...
Just in case, we should consider other alternatives like [https://www.paddle.com](https://www.paddle.com) or similar
Right now we only support `first: Int` and `after: String` for filtering (cursor based relay style pagination). We should also support `offset` and `limit` (Hasura style) and maybe even `keyset`...
Right now, runs will fail on a type mismatch. If the API is flaky and schemas change, it should be handled by `dlt` instead of breaking the pipeline. Some extra...
Currently, everytime we need to include `organization` info we create a new OSO `jwt`. But theres no `refreshToken`, and its not saved (it's created on demand). We should implement a...
Here we could allow users to change settings like `default` organization (which organization will be billed when viewing a public notebook), etc.
Build test infrastructure and test suite for the refactored factory system: Infra: * Mock GraphQL server for testing \`graphql_factory\` * Mock REST API endpoints for testing \`rest_factory\` * Mock GCS...
Update open_collective to use refactored factories consistently: * Use new `graphql_factory` with common abstractions * Remove manual GraphQL code
Migrate defillama to use new `REST` factory