Creating API Operation-objects can currently only be done by using the with_params() constructor. Though, this is unfortunately not obvious and not as well documented as it should be, see #27 Improved in #46
Importing from the API might be improved. Currently it needs deeper knowledge of what you want to import and where to find it. It might make sense to have all API objects reachable from some single point, flattening the import structure
Error handling: Mainly there are three kinds of issues: a) temporary b) needs relogin c) needs user intervention. The thrown errors should make it easy to distinguish between those categories.
Unfreezing request-objects: When sending requests, it frequently happens, that you have a request that will only be a modified version from a previous request. E.g. Iterating over a list of objects to retrieve and only iterating the batch of IDs to retrieve. There is currently no gain from freezing objects, that are used to construct an API request. It only makes it a bit more annoying to compose more complex requests. Mitigated by the .replace() method.
Creating APIImproved in #46Operation-objects can currently only be done by using thewith_params()constructor. Though, this is unfortunately not obvious and not as well documented as it should be, see #27Importing from the API might be improved. Currently it needs deeper knowledge of what you want to import and where to find it. It might make sense to have all API objects reachable from some single point, flattening the import structureUnfreezing request-objects: When sending requests, it frequently happens, that you have a request that will only be a modified version from a previous request. E.g. Iterating over a list of objects to retrieve and only iterating the batch of IDs to retrieve. There is currently no gain from freezing objects, that are used to construct an API request. It only makes it a bit more annoying to compose more complex requests.Mitigated by the.replace()method.