docs(commands): add documentation about missing browser commands

[sipayRT]

No description provided.

[github-actions]

✅ Successfully deployed static

• Docs website
• Storybook

[sipayRT]

need to add https://github.com/gemini-testing/testplane/blob/master/src/browser/commands/switchToRepl.ts command

[shadowusr]

Why is everyone copying this flat weirdly looking table markup with wrong indents, LOL. It wasn't intended, it's a temporary consequence of migrating from yfm. I suggest using proper markup, which will be automatically formatted by prettier e.g. https://github.com/gemini-testing/testplane-docs/pull/26/files

For some reason when tables are formatted this way, Prettier doesn't pick them up. If you add at least one indent, it will format it automatically.

Applies to all pages

[shadowusr]

Another thing we need to come to agreement about is formatting such tables with parameters.

I suggest to wrap param names in backticks and write types in TypeScript style, i.e.
stepName, string.
stepCb, () => Promise<any>

In my opinion it makes things a lot more clear and you can't express much with Javascript types "Object" or "Function". You have no way to express unions with JS types. And generally as far as I understand we're moving towards making TypeScript the primary language in Testplane

[shadowusr]

Let's use typescript in all code blocks?

It won't change a thing here, I know, but I see two reasons why it will be useful:

• When we enable that plugin for automatic Typescript=>JS translation of code blocks, we'll get nice&consistent experience across the whole site. If we keep js blocks, they will be the only ones without the TS/JS switch.
• Anyone in the future will be able to add types / typescript specific syntax

[shadowusr]

Code in all code blocks should be actual valid JavaScript/TS.

This is very important, because only then Prettier will be able to format code blocks inside mdx, depending on the language of the code block. You can see that this code block is already formatted wrong — it uses ' instead of " used everywhere else. ... makes it invalid, should be a comment.

Another reason, again will be that auto TS/JS plugin won't be able to convert code blocks that aren't valid code.

[shadowusr]

Optionally, we can move large enough examples to partial files and import them in ru/en from one place (see my PR). But that's not critical to me, we can keep it as is.

[shadowusr]

Other than that, looks good to me!