Open GaryGapinski opened 2 years ago
Hi, @GaryGapinski . Thanks for the clear reproduction steps. I'm fixing this in the XSpec repo, and Oxygen will eventually pick up the fix as well. I'm glad you have a workaround while you're waiting for the fix. If you prefer not to use a variable, you can consider replacing {1,}
with +
in the regular expression.
Update: Although XSpec patched (#1626) the third-party "skeleton implementation" of Schematron between the released XSpec v2.2 and the future XSpec v2.3 to work around this issue, the patch has been reverted (#1713). As a result, this problem will not go away in XSpec v2.3.
@GaryGapinski : Please continue to use the workaround you found.
I created two test documents. When the embedded regex assertion is uncommented, the XSpec run fails. I have contacted OxygenXML support for assistance.
Moving the regex from the assertion into a variable appears to avoid the XSpec implementation problem.
_Originally posted by @GaryGapinski in https://github.com/18F/fedramp-automation/pull/387#discussion_r826995559_