Jan Čurn
Jan Čurn
Hopefully we will soon: https://github.com/apify/proxy-chain/pull/370
Yeah, definitely
This is really a legal question cc @mnmkng
We're on it, thanks for your patience
Great job, thanks for that! Any chance to merge this soon?
Pls let's discuss the syntax before we implement it, to make sure it's future proof and consistent with other commands. For example: ``` apify download-dataset [ID_OR_NAME] --format csv --limit 100...
Once again we stumbled upon lack of this command, see https://apify.slack.com/archives/C06819MJN9Z/p1710923614723909?thread_ts=1710831604.067589&cid=C06819MJN9Z
Indeed, CLI would need more love and has a lot of opportunities to improve the DX! Two points from my side: - All development needs to be consistent with Actor...
Just fyi, in Actor Whitepaper and SDK/clients, we took care to use consistent naming for "runs", "call", "start" etc. It's important for CLI to be consistent with this too.
I suppose `apify actor run` and `apify actor call` is fine and the latter consistent with `Actor.call` in the Apify SDK. But we need to keep `apify run` and `apify...