noloco-io / python-sdk Goto Github PK

The SDK will return all top-level fields and file fields by default, but any nested relationship fields have to be explicitly requested by an include property on the request. It might be useful to allow a wildcard inclusion down to some nesting level (or maybe restricted just to many to one relationships).

Right now to update a record after reading it the user is required to use a findUnique call, followed by a update call. It would be useful if to update a record the SDK supported updating records by assigning to individual properties on a result, maybe followed by a save call.

When creating a record right now with a relationship field, the target field that the user would like to relate to must already be created in Noloco. It might be useful to enable nested creates where we support creating related records all in one call.

It would be useful if users were able to use list comprehension to iterate over paginated collection results from a findMany call.

When setting up a relationship field between two records, right now it is only possible to run connect: ... on the ID of the target record. It might be useful to enable this on other (unique) fields.

Right now the SDK relies on the user knowing their schemas, either from the GraphQL playground or from figuring them out from the UI. We could give some help here by either auto-generating documentation for them or just giving a help method on the SDK client to give information about schemas.

Right now to delete a record after reading it the user is required to use a findUnique call, followed by a delete call. It would be useful if to delete a record the SDK supported a delete method on the result object.