Qti export #183
Open
Qti export #183
Conversation
This file contains 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
…added a unit test for individual characters, as well as actual questions. The parser also identifies strings with non-ASCII characters and raises an exception.
… through, and can deal with text written on more than one line. All of the tests in qti_parser_test run successfully.
…c tags with the correct format. Had to change the parser unit test to adjust for changes in output.
… raise an exception. But, now it replaces italic tags, as well as bold and line break tags, with the correct formatting, regardless of the case.
…urly fs to parser. Changed error message for image to just text stating that an image is missing.
… of QTI content. It opens the files and creates a new project titled Import.
…to use based on the content type specified by the user.
… the question ids for each question (or will be able to).
…ormer to use. It then creates one project, looks for the first question, and grabs the first answer choice to that question. Then, it looks for the points assigned to each answer choice and normalizes them. Then, it assigns the correct amount of points to the first answer choice. I'll work on iterating through answer choices next.
…oices and select only those for the question being imported.
…es, parse and transform them, and add them to the question.
…earch based on the question id, just like the original function that finds the answer choices. This way, there shouldn't be any worries of answer choices and the corresponding points value not matching.
… of questions with any number of answer choices. Also wrote a unit test, that I will run shortly.
… set up so that it can easily be used by a controller.
… for importing an XML file with questions. Right now, it just has a drop-down menu to select the type of formatting the questions are in.
Added extra line to allow clicking outside of modal dialog to allow exit.
Issue lml#81 Solutions "not ready" info buried too deep
Changed eval statement into a partial render of the assets
Added a check to see if there was no image tag in answer_choice or solution field
|
Rachel why was the pull request closed? |
|
I don't think I closed this. I don't remember ever closing a pull request. An issue, but not a pull request. From what I can tell, you can't reopen it, but I'll see if there's a workaround. |
|
Or, I could click on the reopen & comment button to solve the problem. |
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 is the code for the export function in Issue #14, which discusses importing and exporting questions in a QTI SPQR format.