Difference between revisions of "HSL editor"

From Halon, SMTP software for hosting providers
Jump to: navigation, search
(Scripting editor)
Line 1: Line 1:
The HSL editor functions as an IDE for the [[HSL]] scripting language in order to test and deploy the [[HSL]] code.
The HSL editor functions as an [https://en.wikipedia.org/wiki/Integrated_development_environment IDE] for the [[HSL]] scripting language in order to test and deploy the [[HSL]] code.
== Script listing  ==
== Script listing  ==

Revision as of 07:52, 11 April 2016

The HSL editor functions as an IDE for the HSL scripting language in order to test and deploy the HSL code.

Script listing

The script listing panel list all contexts and scripts available. It also includes some script examples. Some scripts are marked with an exclamation mark, this means you will not be able to open them for editing until converted into a single code block (This is done on the Mail > Flows and Script > edit page).


The button will open the "Search" panel.


The add button allow you to create new scripts and include files.

Scripting editor

There is one scripting editor windows for each script. Each script is opened independently of each other, and one script does not see changes done in another script (eg. using include) until that script is saved.


The save button will save the script to the running configuration. It will also perform syntax checks, any error found may be overridden and saved anyway, however that is not recommended. If you receive a error while saving. Please consult Halon's support team.

Show changes

The show changes button will show changes made in the script in regards to the current running configuration.


The test button will do syntax checks and will show the output in the console.

Run in sandbox

The run in sandbox button will execute the code in a "core language" sandbox (with the pre-/postamble script attached). The pre-/postamble script contains some of the variables and functions needed to simulate the context. Note that all function in the "core language" will be executed (that includes eg. http() calls). In order to setup a working environment uncomment and set the correct value for each variable.


The console panel shows all messages generated by the editor. If the console is minimized it will show a badge with the number of log messages unread.


The search panel searches in all code (currently saved on the server side) and shows the line with a surround context of each match.