Nikan's Notebook

Notion Integration Kanban

3 min read

Archive

  • maybe also resync the database once every week??
  • ok locally developing this would be hard since i cant get the api integrations to local host, or i could but i dont want to setup the networking since i already have the EC2 running.
  • setDate does not wrap around the month right now, if i wanna do it for archiving ill have to fix it probably — nvm this apparently automatically is handled by the date objects in js

Complete

  • bump up priority everytime the deadline is extended
    1. get priority function
    2. update priority
  • testing
  • bug data for recursion was weird
  • BUG: event cases are not working sth weird is happening
  • Bug: if the task is done, it still puts it in the deadline extension bucket
  • maybe also have a custom pushed back deadline for long running tasks, but i would need to put in long running tasks in first before i do this, right now 2 day default should be fine
  • integrate long term lists
  • change function names to be more intuitive
  • Bug: weekly archive is not triggering
  • add winston for easy logging
  • weekly archive list change
  • Refractor everthing to a OOP model
  • project is pretty small move to typescript?
    1. helper functions
    2. DB functions
    3. server functions
  • maybe add a recurring propertie and a recurringByDays property so that I dont have to sync it manualy
    1. set up is recurring on notion as a property
    2. add change recurring to the DB functions
  • make algorithm flowchart so that i can tell what the fuck is going on
  • refractor code so to use get name, get status, get deadline function instead of making a big notion call everytime to make it more readable
  • still breaks backend - to be seen
  • Keep Track of tasks with Due Dates and extend them if the due data is passed
    1. update the DB with the new due date
    2. have to have a funciton watch for due date changes
    3. if they had deadlines, delete them from the deadline array as well
  • for done stuff, keep track and archive after a week
    1. update the DB when the task is archived
    2. have the last modified/marked done in the DB, prepopulate at init and schedule timers
    3. add new tasks added to the done columen
      1. from created page
      2. from page_properties_updated
      3. check to be non recurring
    4. remove them from the markedForArchive set when status changed
  • weekly clear out archives
    1. update and delete from Database
    2. have a last cleared table/variable in the DB, pull it and based on that schedule clearing
  • DB keeps track of available tasks
    1. recurring tasks
      1. update the DB when the Task has recurred with the new Status and Deadline?
  • BUG: its updating anything with a deadline right now instead of just the specific.
  • Add RDS integration for token verification persistance.
  • github actions docker push and aws deploy
  • authenticate
  • AWS ALB routing

Working on it

  • 1. [ ] add font sizing to the different priorities and the priority changes as the deadline gets pushed back TRMNL Kanban
  • Bug: changing deadlines makes it crash
  • it still crashes
  • i did delete a health check rule, if sth goes wrong its that

to Start

  • deleted pages, update DB and delete them from sql, sometimes i create shit accidentally, if the eventtype is page deleted delete from DB
  • CICD: use STS instead of manually SSH ing into the instance, or tailscale, but i wanna use sts to learn

Graph View

Backlinks