Closed djplaner closed 1 year ago
Aim being to figure out what the controller does and how it should be done in Svelte
Goes into the main.ts - called before the App.
If it's not a modulesPage or a course, don't add the app.
If it is pass the courseId and editMode to the component
main.ts passes context as props to <CanvasCollections courseId= editMode=>
After some initial configuration the process is
initialiseConfigPage
parseNewPageBody
div#canvas-collections-representation
Current structure is
CanvasCollectionsRepresentation
<CanvasCollectionsRepresentation>
<CollectionsNavigation>
</CollectionsNavigation>
<div.cc-message>{message for current collections}</div>
<CollectionRepresentation>
</CollectionRepresentation>
</CanvasCollectionsRepresentation>
To do
With multiple collections with Cards representation, changing between them will change the name of the collection, but will NOT modify the representation of the cards - still showing the same cards as initially loaded.
Check this by adding multiples - CONFIRMED
Suggesting the problem is that the {collection} used for the name of the collection is reactive. What's not reactive is the code that's generating the HTML for the tables or cards
Make the calculation of moduleIds reactive by adding $:
Implementation
Status - working on deleting a collection. Most of it appears to be working, but there's something wrong with the reactive stuff. It apepars to be trying to access a representation for a collection that no longer exists
Longer term tasks
Support
CanvasCollections
UniversityDateCalendar
CanvasCollectionsConfiguration
CollectionRepresentation
ModuleConfiguration
Cards
Assessment table
Table evolution
Longer term
Canvas collections