A developer's front end for Qorus Integration Engine
The extension makes possible remote deployment of edited Qorus source files directly from the VSCode editor. Qorus server can be attached and interface code debugged.
How to use
Configuration data and corresponding tree view
In order to work with the extension a project must be open in the VSCode editor. By project we mean the root directory of a project (the root of a git repository, for a typical example).
Next, development environments and their Qorus instances have to be configured. To do this, use the configuration tool [Project configuration] in the Qorus manager webview that can be opened by clicking the violet hexagon [Q] icon at the right top corner (it is visible only if at least one project file is open). If the project configuration is done for the first time some initial configuration data is automatically generated to be modified by the user.
The configuration data structure is three-level: Environments -> Qorus instances -> Qorus instance properties. Each development environment can have several Qorus instances and each Qorus instance has a main URL (URL of the Qorus engine itself) and, optionally, several custom URLs.
Based on the configuration data a Qorus instances tree view is provided in the Explorer pane. Switching to the Qorus instances tree view is done by clicking the hexagon [Q] icon in the activity bar. The configuration data is stored in the file named qorusproject.json at the root directory of the project and the file is not supposed to be edited manually.
More projects (directories) can be open at the same time. When editing alternately files from different projects the Qorus instances tree view changes accordingly.
There are three deployment actions:
The deployment is targeted to the Qorus instance that is currently set as active. A Qorus instance can be set as active in the Qorus instances tree view, either from the context menu over a Qorus instance node (second level node) or simply by clicking the Qorus instance node directly. Active Qorus instance is marked by the green light icon. Of course, at most one Qorus instance can be active at a time, setting another instance active inactivates the instance that was active before.
You can also remove interfaces from the active Qorus instance. To this end, use the [Delete interfaces] Qorus manager menu item.
If a Qorus instance requires authentication (and the user has not yet logged in that instance) the
The context menus over the Qorus instance tree nodes offer also the following commands
Making a release package
Use the Qorus manager webview menu item [Make release] to create a release package. Before using it the source repository must be 'clean': all changes must be commited and the working branch synchronized with remote (everything pushed/pulled). You can create either a 'full release package' containing all source files or an 'incremental release package' containing only files that have changed since the selected commit. Once you have create a package you can also save it to (re)use it later.
The sessions are configured in
To start debugging prepare launch file, select a configuration from drop box and
The launch file data structure is explained by the following example: