Getting Things Done flow inspired app
- Make Sotable.js work
- Create input for inbox (add to array of ideas)
- Create inbox-idea component
- Refactor QuickFullScreen otside the Quick component... Make it App level
- Start working on Nest
git clone <this_repo>
cd gtd-app/client-spa/gtd-app-spa
npm install
Copy the contents of gtd-app/client-spa/gtd-app-spa/src/lib/Sortable.zip to gtd-app/client-spa/gtd-app-spa/node_modules/sortablejs and replace all.
npm run dev To start dev server
Possible memory leak
As the fix for correcly smooth-collapse the IncubatorProject component implies creating a new Sortable for a new element each time the container opens (inside an {#if block}), the memory for those new Sortables could be incrementing each time the user opens a Project component. This seems to be the case, however it seems that the garbage collector triggers and clean up some of it. Is this enough?
Could be a way for destroying the Sortable on a Project-close event?
Could be a way for re-using the Sortable?
Is this even worth the worry as the minimum impact and low scenario for reproduction? (I dont't think so)
