Closed Cutuchiqueno closed 7 months ago
There is an important restriction on the xsl:message
auto-completion:
It only offers simple-variables and _complexvariables options in the auto-complete list for variables declared before the cursor position and inside the immediate scope of the current XSLT instruction element.
In most cases, this restriction is helpful because it helps avoid overwhelming the user with too much information in the xsl:message output in one go. Each separate xsl:message
has it's own header to it's clearer when the output has come from.
That said, I've found this can be an annoyance for example when I want to print out the values of global xsl:param
and xsl:variable
declarations.
I will improve the documentation to mention this restriction.
Thanks for the clarifications. It works for local variables in scope, now that I looked out for situations in which local variables exist.
The section on debugging in the documentation recommends to use special auto-completion for
xsl-message
and shows 3 options blank, simple-variables and complex variables. However, when I instagate auto-completion onlyblank
exists. Thus, I am not able to generate the corresponding debugging template.