Improvements for ESQL Code Formatting

Wow, my code lines were formatted by comment engine 😀

It was the original example:

SET rowTemp.businessIdentifierList[] = LIST{
	'asnHeader.asnNumber', 
	'asnHeader.customerPONumber',
	'asnHeader.expectedDeliveryDate',
	'asnHeader.billOfLading'
	};

1. multi-line command could a very long code line with line breaks:

SET rowTemp.businessIdentifierList[] = LIST{

'asnHeader.asnNumber',

'asnHeader.customerPONumber',

'asnHeader.expectedDeliveryDate',

'asnHeader.billOfLading'

};

Now, that command above after a "Format" will be flattened to the position of "SET ..." which spoiles readability.

4. two empty lines in the beginning of ESQL file: the main problem is with that, it is happening a repeated way, adding 2 more lines with every Formatting.

5. label with or without space: editor and ESQL parser works fine both way, but Formatting cannot indent a loop properly with label without a space after the colon separator, for example:

LABEL:WHILE i < 1 DO

SET i = 1;

END WHILE;

will be indented a wrong way.

Regards,

Tibor

Thank you for taking the time to raise this enhancement request. Some comments on the details:

1. "configuration for indenting multi-line commands". It is possible to highlight multiple lines and from the right-click options choose "Shift right" or "Shift left" to indent multiple lines. Is this what you had in mind or is something further needed?

2. "readability options: like comma + space; operator + space; keywords + space should be configurable"

Our understanding is that this is asking for auto beautification of adding spaces around a plus sign or around a comma or clause etc. Good suggestion.

3. "removing of empty lines are automatic now, but it could be configurable". Could see how this could be helpful and automatable.

4. "adding 2 empty lines in the beginning of ESQL is automatic - why?

This is to intentionally help make it clear that variables can be declared at the global scope outside a module ... with enhancement suggested in item 3 they could be removed easily if users don't like this styling.

5 'label:statement' is not handled properly only 'label: statement' is identified

This is an editor enhancement to allow the lack of a space after the label.

Status of the idea is updated to Future Consideration.