-
The buggy case is presented in this unit test code.
Basically, the `` works but results in following output
```
test1 helloreplaced text
```
So the beginning of the text ("This is") is lost som…
-
This test case will show the problem. The output is now `XYtest1` even though it should be `Xtest1Y`. I think it is because the text nodes get `siblingPosition` of -1 and the `xsl:value-of` gets bigge…
-
An XSL template that includes the following "pass-through" rule will generate a spurious `Combinator` error in `xslt::from_document` (using the sample code for the xrust:xslt module, simply with this…
-
The biggest headache when debugging XSLT stylesheets is working out which template rules have been invoked in response to an `xsl:apply-templates` instruction (I'm hitting this frustration right now w…
-
### Describe the Bug
If i add a Transform XML Action in a Logic app which uses custom code local function (.NET 8), it fails with this error:
Result: Failure
Exception: System.InvalidOperationExcep…
-
An XSL template with a trivial Path expression
```
`
```
fails to compile in `xslt::from_document` (using the example code in the xrust::xslt documentation) with
```
extra characters …
-
I just included an test example in the editions.xsl template that links the commentary if existing.
https://github.com/bundesverfassung-oesterreich/bv-static/blob/a1c2fa4d5de2a8bbcc5468126c3f9205a248…
-
The current XSLT Step template field does not support variables. This would be useful since the template could be loaded on deploy from an external file.
Imported Issue. Original Details:
Reporter: g…
-
The current XSLT Step template field does not support variables. This would be useful since the template could be loaded on deploy from an external file.
Imported Issue. Original Details:
Jira Issue …
-
The current XSLT Step template field does not support variables. This would be useful since the template could be loaded on deploy from an external file.
Imported Issue. Original Details:
Jira Issue …