Open marcellamaki opened 2 weeks ago
Hi, @marcellamaki can I work on it ?
Hi @abhirupPann, thanks for volunteering! This issue is not meant for contribution, but there are another contributing opportunities. See the contributing guidelines including links to issues suitable for contribution for each repository here:
You can also see the list of unassigned "help wanted" or "good first issue" issues across all repositories.
Overview
The lesson management workflow (adding resources to lessons) is being updated to use the similar side panel management UX that we introduced in quizzes in 0.17. This issue is one way that we are refactoring the selection of resources and folders, tracking and updating local state, etc. to have a cohesive experience across lessons and quizzes.
The purpose of this issue is to do as minimal a refactor as possible of the existing
ResourceSelection
component, currently used in quizzes, to allow an MVP use case in lessons without breaking the current quiz functionality. For this issue, you should create an<UpdatedResourceSelection />
component. The purpose of this is not to rearchitect the entire idea of the resource selection, but rather to find the simplified version that can be used in the updated lessons case. Extending the component functionality for the new features of quizzes (i.e. question selection), or even using it in quizzes at all, will happen later and is beyond the scope of this issue.Related but out of scope tasks and issues:
ContentCardList
withKCards
/KCardGrid
Description
This new
<ResourceSelection />
should be something in between the current version, which is closely connected to quizzes, and theContentCardList
, a child component that renders the resource cards and their corresponding selection, although the state management lives outside of the list.The component should:
Additional technical considerations:
Variations of the side panel with resource selection
Goals
The first goal of this issue is to further refine the spec in collaboration with @marcellamaki with inputs from @nucleogenesis and @rtibbles to make final decisions around things like the selection rules. Note that once QA starts working on this and testing, we may encounter a few unpredictable edge cases and need to make further refinements.
The second goal is to update the component:
ResourceSelection
component that is the most simple version, that could be used in lessons. This could be done by copying all of theResourceSelection
to something likeUpdatedResourceSelection
and deleting code, or by creating a newUpdatedResourceSelection
and selectively copying and updating the functionality