-
Bug
-
Resolution: Done
-
Critical
-
0.61
-
None
-
None
Example:
artificer> query "/s-ramp/wsdl/Operation[xp2:matches(@name, 'submit.*')]"
@Arguments contains /s-ramp/wsdl/Operation[xp2:matches(@name,submit.*
artificer> query "/s-ramp/wsdl/Operation[xp2:matches(@name, \'submit.*\')]"
@Arguments contains /s-ramp/wsdl/Operation[xp2:matches(@name, 'submit.*')]
artificer> storedQuery create --name FooQuery5 "/s-ramp/ext/${type}"
@Arguments contains /s-ramp/ext/
artificer> storedQuery create --name FooQuery5 "/s-ramp/ext/\${type}"
@Arguments contains /s-ramp/ext/\${type} (note that for this one, it explicitly included the escaping slash)
If at all possible, arguments should not require those quotes to be escaped, at least when surrounded with double quotes. Alternatively, include some sort of boolean field on @Option and @Arguments that allows special chars to be used.
- blocks
-
FUSEDOC-986 CLI fails to query S-RAMP repository
- Closed
- is related to
-
AESH-330 Allow ${foo} syntax to be either escaped or optionally skip variable substitution
- Resolved