To create a preview for INPUTs/Maps inside the VSCode client, the language server needs to provide some structural information about INPUT statements and maybe some helpful code actions to assist developing those.
The endpoint should return a consumer friendly structure, not the raw syntax tree.
[x] Draft and create an endpoint that can be consumed #453
[x] Include statement level attributes on the elements, if they're not overwritten by an element attribute #461
[ ] Include FORMAT statement attributes (esp. LS and PS) on the elements, with lowest priority if overwritten by either statement or element attribute
[x] Understand RULEVAR and INCDIR so that these statements in Maps don't come up as new diagnostics #462
[ ] Add some INPUT specific refactorings and diagnostics (e.g. replace with repetition, duplicate array line, make intensified, replace 5 blanks by 5X, position element explicitly (10T), ...)
[x] #456 Make sure hovering works on input operands
[ ] Add effective attributes to input operand hover
To create a preview for INPUTs/Maps inside the VSCode client, the language server needs to provide some structural information about INPUT statements and maybe some helpful code actions to assist developing those. The endpoint should return a consumer friendly structure, not the raw syntax tree.
FORMATstatement attributes (esp.LSandPS) on the elements, with lowest priority if overwritten by either statement or element attributeRULEVARandINCDIRso that these statements in Maps don't come up as new diagnostics #462replace with repetition,duplicate array line,make intensified,replace 5 blanks by 5X,position element explicitly (10T), ...)