Skip to content

Commit

Permalink
Remove deprecated content from Wiki pages
Browse files Browse the repository at this point in the history
Signed-off-by: Dominik Jelinek <[email protected]>
  • Loading branch information
djelinek committed Nov 28, 2023
1 parent 7e499b5 commit 54d5249
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 32 deletions.
21 changes: 0 additions & 21 deletions wiki/OpenDialog.md

This file was deleted.

12 changes: 1 addition & 11 deletions wiki/Page-Object-APIs.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
In order to keep everyone from having to go through the VS Code DOM, which is quite complicated, the framework provides page objects to work with parts of VS Code directly.

See the individual page object pages below for quick usage guide. For complete API reference, you can generate typedoc with ```npm run doc``` and check the ```docs``` folder.
See the individual page object pages below for quick usage guide.

##### Activity Bar
- [[ActionsControl]]
Expand Down Expand Up @@ -58,13 +58,3 @@ See the individual page object pages below for quick usage guide. For complete A
- [[Workbench]]
- [[Input]]
- [[DebugToolbar]]

***

##### Native Dialogs
There is also a limited support for handling native dialogs done via virtual key presses. This requires installing the module `vscode-extension-tester-native` alongside the main extension tester package.

If you venture into this territory, make sure the application does not lose focus and you are not touching the keyboard while a native dialog is being handled.
- [[OpenDialog]]

Extest now also contributes new commands to open files or folders without using native dialogs. If you simply need either open, we recommend using the commands instead of the open dialog for increased stability. Learn more about opening files and folders [here](https://github.com/redhat-developer/vscode-extension-tester/wiki#opening-files-and-folders).

0 comments on commit 54d5249

Please sign in to comment.