Long form schema 3.0.0 #27
Closed
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 pull request updates the quest definition schema and example data to version 3.0.0, introducing new question types, improved dependency handling, and stricter schema validation. The changes enhance the flexibility and robustness of quest definitions, allowing for more complex question structures and dependencies.
Schema enhancements and validation:
example.jsonandschema.jsonto version3.0.0, reflecting significant schema changes. [1] [2]additionalProperties: falseto all major schema objects (Element,AnswerChoice,Question, etc.) for stricter validation and to prevent unexpected fields. [1] [2] [3] [4] [5]Question types and answer choices:
MultipleChoice(select multiple options) andTextEntry(free-form text answers), with corresponding enum and documentation updates.quest_answer_choicesonly for non-TextEntry questions, using conditional validation logic.Dependency handling improvements:
dependencydefinition and updatedquest_answer_dependencyto support both single and multiple dependencies (AND logic), allowing questions to depend on multiple previous answers. [1] [2] [3] [4]Example data updates:
MultipleChoicequestion about sidewalk amenities and oneTextEntryquestion for additional notes, demonstrating the new schema features.Formatting and clarity:
Let me know if you'd like to discuss how to use the new dependency system or question types in your code!