Skip to content
This repository has been archived by the owner on Nov 21, 2019. It is now read-only.

Apply patch to fix Schematron attribute paths #11

Merged

Conversation

thewilkybarkid
Copy link
Contributor

@thewilkybarkid thewilkybarkid commented Mar 4, 2019

Applies Schematron/schematron#81 (refs libero/jats-support#1 (comment)).

(@FAtherden-eLife took a quick look at the patch and was happy.)

@thewilkybarkid thewilkybarkid added the bug Something isn't working label Mar 4, 2019
@thewilkybarkid thewilkybarkid added this to the 0.2.1 milestone Mar 4, 2019
@thewilkybarkid thewilkybarkid requested a review from a team as a code owner March 4, 2019 11:10

echo "Downloading {$patch} to {$patchTarget}\n";
$filesystem->copy($patch, $patchTarget);
$repo->apply($patchTarget, ['verbose' => true]);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think by default the patches remain tracked in Git as a change not staged for commit. The interaction with updates should work because then a git reset --hard will be performed.

new Failure(
'Attribute must not be empty',
6,
$xpath->query('/example:parent/example:child/@attribute')->item(0)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this enough context? I guess the DOMNode contained in Failure has some information about what element it was on?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, since it's retrieved from the document.

@thewilkybarkid thewilkybarkid merged commit 3280f35 into libero:master Mar 6, 2019
@thewilkybarkid thewilkybarkid deleted the schematron-attribute-path branch March 6, 2019 13:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants