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
As we update the selection and state management for lessons and quizzes in the side panel for coach resource discovery, we will be starting with the lessons, as they have a simpler state management (no sections, no question ids) as compared to quizzes.
The first step is to review the ResourceSelection component, and to create a minimal version of a composable, that does selection/state management for the resource selection panel state. This composable doesn't need to be in the top levels /composables folder, because it won't be widely shared beyond selection/state management in coach. The purpose of creating a composable is to keep the code modularized and manageable -- it's essentially just to create some helper methods that could be tweaked further for quizzes or shared for both lessons and quizzes.
Start by reviewing the code in ResourceSelection and useQuizCreation, and run develop to understand how the code is connected to the UI/UX within quizzes specifically.
Acceptance criteria
Create a useResourceSelection() composable (or if you have a better name suggestion, propose it), that takes the core parts of selection and state management
The text was updated successfully, but these errors were encountered:
Overview
As we update the selection and state management for lessons and quizzes in the side panel for coach resource discovery, we will be starting with the lessons, as they have a simpler state management (no sections, no question ids) as compared to quizzes.
The first step is to review the
ResourceSelection
component, and to create a minimal version of a composable, that does selection/state management for the resource selection panel state. This composable doesn't need to be in the top levels/composables
folder, because it won't be widely shared beyond selection/state management in coach. The purpose of creating a composable is to keep the code modularized and manageable -- it's essentially just to create some helper methods that could be tweaked further for quizzes or shared for both lessons and quizzes.Start by reviewing the code in
ResourceSelection
anduseQuizCreation
, and rundevelop
to understand how the code is connected to the UI/UX within quizzes specifically.Acceptance criteria
useResourceSelection()
composable (or if you have a better name suggestion, propose it), that takes the core parts of selection and state managementThe text was updated successfully, but these errors were encountered: