Convert a solutions file on its own when no questions file is beside it - #26
Merged
Merged
Conversation
… is beside it (t30)
… is beside it (t30)
… is beside it (t30)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A solutions file with no questions file beside it is skipped by
runandcorpus(solutions without questions, t20), so UCL_MechEng/Tutorial_2_Solutions.pdf is not converted at all. A document of solutions alone is a set in its own right - in2lambda's spec engine runs over one (t48: a doubled solution is reported, not refused), and a lecturer may hold only the solutions. Where pair.of finds no questions file, run the solutions file as a single-source document, with the stage line sayingno questions file named X beside it; converting the solutions alone, and let the spec writer know in its prompt that the document holds solutions and no questions, so it writesquestionselectors for the markers. corpus records the row as any other document. Tests in tests/test_pair.py and tests/test_pipeline.py. Done when Tutorial_2_Solutions.pdf produces a built or faulted row, not a skipped one.Workbench ticket t30.