feat: Support adding questFields
to a questStep
; display form fields within a quest
#113
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.
What changed?
questSteps
table toquestFields
table by supplying an array ofquestFields
to afields
column for a stepQuestStep
component to handle displaying the step title, description, and fieldsQuestStep
component within the admin and on user-facing questsquestFields
to aquestStep
via the Admin UICheckbox
component with support forlabel
anddescription
Why?
Ongoing work to provide v1 experience. Pre-defining fields that can be re-used across multiple quests will help enforce consistency and allow us to define canonical inputs for common entries like email and name.
How was this change made?
Removed old tables, connected new data, tested end-to-end to make sure everything works.
How was this tested?
Manual testing.
Anything else?
First part of #111; will follow-up with saving user data from form fields.