Jan Čurn

Results 80 comments of Jan Čurn

For reference, working document is now at https://www.notion.so/apify/New-CLI-Design-a8751a53896e472a9c8f474669f6f5d5

@mtrunkat is the schema validation code somewhere accessible?

Plus it should validate that the schema is valid. But who will validate that the validator of the schema is valid, eh? :)

+1 to this. In Actor specification we suggested to use `--json` to force JSON input/output for all commands.

No polling is Slack please. We need to prepare a comprehensive and consistent specification of the new CLI, agree on the interface, and then decide in which order we'll add...

Points from me: - support for OpenAPI specs for the api - well integrated into [https://docs.apify.com/](https://docs.apify.com/) - provides code examples in our client libraries for Node.js, Python, and ideally also...

Perhaps we can just have a script to parse the READMEs and generate the nginx config automatically? Completely outside of Docusaurus. It could looks like: ``` --- title: Getting started...

Hey, so basically we'll be able to override the menu text using the `siderbar_label` option, and the `title` will be kept as is (used for page title, H1 if there...

Okay, but if `title` is present, it will be used for page title and OG description? I think it would be good to still have it as a way to...

I think it's more transparent to keep the `title` in content, rather than the H1s, so I'd clean the H1 if they are the same. It's clearer that's what's used...