You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This QuestActionSubForm component is quite complex. Quick break down:
Has multiple configurations and error states
Per chosen action
Multiple different field configurations are used
Values are overridden if action is changed and some overrides require complex state resets
Multiple different validation rules/schemas are used
Some values are optional in some configurations while required in some
Nested validation applies to some specific actions
URL format and Content ID configurations (optional/required) validations for different platforms ex: twitter/common/discord/chain-events.
Default/gated value handling for chosen actions. Some actions only allow specific values.
Conditional instructional messages that change how end-users will interact with the selected action.
Per chosen aura limit <> repetition schedule
Some actions only allow specific repetition types ex: Tweet Engagement
Complex participation limit validations. The repetition counts are different for chosen schedulea and per chosen action.
Per chosen quest type, listed actions change i.e channel vs common quest.
and many more configurations as we continue to add more quest actions and tailoring existing ones to be more specific.
This ticket is about simplifying the component to be more dynamic, accommodate more configurations and be maintainable more easily than in its current state.
--
Use URL() where it can be used
The text was updated successfully, but these errors were encountered:
Description
The component in discussion
packages/commonwealth/client/scripts/views/pages/CreateQuest/QuestForm/QuestActionSubForm/QuestActionSubForm.tsx
This
QuestActionSubForm
component is quite complex. Quick break down:Tweet Engagement
and many more configurations as we continue to add more quest actions and tailoring existing ones to be more specific.
This ticket is about simplifying the component to be more dynamic, accommodate more configurations and be maintainable more easily than in its current state.
--
Use URL() where it can be used
The text was updated successfully, but these errors were encountered: