for_statement
--- EACH
--- identifier
--- where_clause
...
--- body
------ abl_statement
...
We ran into problems when trying to implement code formatting logic for this structure. The main issue is that header nodes are under the same level as body node. As body starts with the first statement inside it, and not with : symbol, for formatting proposes we have to use whole range of for_statement node. And this leads to further issues when trying to create formatting algorithm.
The best solution for us would be to have additional node (e.g. for_header). Something like this:
for_statement
--- for_header
------ EACH
------ identifier
------ where_clause
...
--- body
------ abl_statement
...
Currently we have this FOR statement structure:
We ran into problems when trying to implement code formatting logic for this structure. The main issue is that header nodes are under the same level as
body
node. Asbody
starts with the first statement inside it, and not with:
symbol, for formatting proposes we have to use whole range offor_statement
node. And this leads to further issues when trying to create formatting algorithm.The best solution for us would be to have additional node (e.g.
for_header
). Something like this: