Rapise Objects and Files Metadata for Code Completion

Rapise scripts and engine are mostly implemented in JS. Some people prefer to use 3rd party editors for scripting. This is helpful when integrating Rapise tests into bigger development pipeline together with other scripts and config files. Here we explain where information about objects and types is provided for Code Completion/Intellisense support in 3rd party editors.

We designed these play.cmd & record.cmd so that you may do record & playback from external tools, such as vscode or notepad++.

We did even more. All metadata related to tests and internal Rapise functions is stored explicitly in .json format. Let's go over places where this information is stored. For given test, for global objects and for ActiveX types.

1. All global objects are explained in <rapise setup>\Engine\Metadata\GlobalObjects\*.metadata. So when someone types "Global.", code helper first checks for ....GlobalObjects\Global.metadata2. Code helper tracks object type and SeS("myObj") function. So if you have one of these statements:

var myObj = SeS('myObj');
myObj.*

or

SeS('myObj').*

Where '*' depicts the place where one is currently typing and where code completion is to appear.

In such cases there is a way how to find object type information. Find 'Memory_clear' in the Objects.js. It is actually a JSON file, but in JS format. Only difference is presence is variable declaration:

var saved_script_objects = {.....

so if you trim everything before to 1st '{' then you will get pure JSON. Here you should be able to find an object definition and take it's object_type, i.e.: