Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the test suite to be included via Composer so we can more easily keep it up to date with https://github.com/microformats/tests, per #50.
The comparison of parsed mf2 to expected output now compares the complete array, not just the 'items' key. I took a stab at better array comparison, since the === comparison expects the array indexes to be in the same order.
Unfortunately these changes bring the number of passing tests to zero, but hopefully a lot of those are minor. For example, I know that php-mf2 puts the "T" separator in parsed dt- values, but the test suite expected output does not (see discussion), so most date values will have that discrepancy.
The updated array comparison should verify that every value in the expected output appears in the parsed output, but does not account for the parsed output having more than the expected output. The array comparison could be run twice (switching the array parameters) but I wasn't sure if that was desired. And I thought it was more important to make sure the parser returns at least the expected output.