More comprehensive synchronization of expand tests in toRdf #422
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rubensworks
approved these changes
Mar 17, 2020
This was referenced Mar 17, 2020
…o toRdf/e0xx which come from expand/00xx.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 should make all expansion tests have equivalents in toRdf. Tests expand/0xxx are no toRdf/exxx. Old expand/e0xx tests are now expand/erxx and copied to toRdf.
Fixes PR #418.
Fixes PR #419.
I was going to avoid such hard duplication, but it's leading to too much confusion, and this establishes a naming scheme that should help keep things in order.