Due to the nature of XML, such files can be noisy and unnecessarily long, so some code folding could help this case and lessen the cognitive load and comprehension of Citrus XML test files.
One simple example would be the echo action. The code folding could turn
<echo>
<message>Some message to print</message>
</echo>
into
<echo>Some message to print</echo>
and hide the <message> tags.
Tasks
Collect the tags that could be folded.
Implement code folding. It might be something similar that goes on in the Just Kitting plugin.
Folding candidates
[x] echo in XML and Spring XML
<echo>
<message>Some message to print</message>
</echo>
Some message to print
- [x] load properties in XML and Spring XML
```xml
<load>
<properties file="classpath:some/file" />
</load>
<load properties: classpath:some/file />
Summary
Due to the nature of XML, such files can be noisy and unnecessarily long, so some code folding could help this case and lessen the cognitive load and comprehension of Citrus XML test files.
One simple example would be the echo action. The code folding could turn
into
and hide the
<message>
tags.Tasks
Folding candidates
@file
in Spring<receive message "classpath:org/citrusframework/actions/payload.groovy" at "myMessageEndpoint" />
@file
in Spring<validate by groovy script "classpath:org/citrusframework/jms/integration/helloValidationScript.groovy" />
purge-channels.channel
tagspurge-endpoint.endpoint
tags.<jms:purge-jms-queues ref:myQueue, name:JMS.Queue.1 /> or <jms:purge-jms-queues myQueue, "JMS.Queue.1" />