-
Notifications
You must be signed in to change notification settings - Fork 1
Quest Definition Schema Version 3.0.0 #25
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
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
1d6a08e
Add multiple dependency quest definition example
uw-amy-bordenave 8afa54c
Upgrade to schema 3.0.0 with support for multiple dependencies
uw-amy-bordenave e93ebe3
Add conditional requirement for quest_answer_choices based on quest_t…
iamrajeshk 425975b
Merge branch 'main' into quest-definition-schema-3.0.0
uw-amy-bordenave ddccf79
Auto-generate image READMEs
github-actions[bot] 2f7a95e
Merge branch 'main' into quest-definition-schema-3.0.0
uw-amy-bordenave 2a83840
Fix `quest_answer_choices` requirement logic
uw-amy-bordenave af89ce2
Replace "GoInfoGame" with "AVIV ScoutRoute"
uw-amy-bordenave 3865c8d
Add missing `required` fields to `dependency` section
uw-amy-bordenave 2991e93
Update `quest_answer_choices` description
uw-amy-bordenave fe51a3c
Update `question_id` examples
uw-amy-bordenave File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you get more into GitHub, here's a friendly PR etiquette tip: I'd avoid mixing cosmetic and content changes in the same PR. The noisy diffs may divert attention from the "meat" of the PR. Good PRs usually have a narrow focus/scope.
In this case, I'm also a little worried that someone may inadvertently reverse the changes with some automated formatting tool—some editors run these automatically these days.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the heads up and the best-practices tip :)
In this case, that's exactly what happened - ran the Prettier formatter in VS Code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to check in that Prettier config to this repo so tools don't fight with each other over formatting.