Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: quizBankID should be a number #209

Open
swashbuck opened this issue Jan 17, 2025 · 0 comments · May be fixed by #210
Open

Documentation: quizBankID should be a number #209

swashbuck opened this issue Jan 17, 2025 · 0 comments · May be fixed by #210
Assignees

Comments

@swashbuck
Copy link

swashbuck commented Jan 17, 2025

Subject of the enhancement

According to the schemas, _quizBankID should be a number. We should update the documentation so that this is reflected. In the readme, the number is shown as a string with quotes.

>>**\_split** (string): This is a comma-separated list of numbers corresponding to the number of questions to be drawn from each identified block. The *position* of the numeral in the list corresponds to the **\_quizBankID** assigned to a block. The *value* of the number determines how many questions to retrieve randomly from that particular quiz bank. For example, a **\_split** with a value of "2,1" would pick 2 questions from bank 1 (`"_quizBankID": "1"`) and 1 question from bank 2 (`"_quizBankID": "2"`).

_split (string): This is a comma-separated list of numbers corresponding to the number of questions to be drawn from each identified block. The position of the numeral in the list corresponds to the _quizBankID assigned to a block. The value of the number determines how many questions to retrieve randomly from that particular quiz bank. For example, a _split with a value of "2,1" would pick 2 questions from bank 1 ("_quizBankID": "1") and 1 question from bank 2 ("_quizBankID": "2").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Reviewing
Development

Successfully merging a pull request may close this issue.

1 participant