Follow-up to #719
As a follow-up to the work in #719 (adapting the SDK to apify-client v3), we should go further and completely replace the custom models defined in the SDK with the generated models from apify-client-python.
Context
The SDK currently defines its own Pydantic models in src/apify/_models.py, including:
ActorRun, ActorRunStats, ActorRunUsage, ActorRunOptions, ActorRunMeta
FreeActorPricingInfo, FlatPricePerMonthActorPricingInfo, PricePerDatasetItemActorPricingInfo, PayPerEventActorPricingInfo
ActorChargeEvent, PricingPerEvent
PricingModel type alias
Webhook
Now that apify-client-python v3 provides fully typed, OpenAPI-generated models (e.g. ActorRun, ActorRunStats, ActorRunUsage, Pricing*, ...), we should use those directly instead of maintaining a parallel set of models in the SDK.
Tasks
Follow-up to #719
As a follow-up to the work in #719 (adapting the SDK to
apify-clientv3), we should go further and completely replace the custom models defined in the SDK with the generated models fromapify-client-python.Context
The SDK currently defines its own Pydantic models in
src/apify/_models.py, including:ActorRun,ActorRunStats,ActorRunUsage,ActorRunOptions,ActorRunMetaFreeActorPricingInfo,FlatPricePerMonthActorPricingInfo,PricePerDatasetItemActorPricingInfo,PayPerEventActorPricingInfoActorChargeEvent,PricingPerEventPricingModeltype aliasWebhookNow that
apify-client-pythonv3 provides fully typed, OpenAPI-generated models (e.g.ActorRun,ActorRunStats,ActorRunUsage,Pricing*, ...), we should use those directly instead of maintaining a parallel set of models in the SDK.Tasks
src/apify/_models.pythat have equivalents inapify-client-pythonsrc/apify/storage_clients/_apify/_models.pyfor models that may now have client equivalents