Skip to content
Snippets Groups Projects
  1. Dec 07, 2022
  2. Dec 06, 2022
  3. Dec 05, 2022
  4. Nov 29, 2022
  5. Nov 28, 2022
  6. Nov 25, 2022
  7. Nov 24, 2022
    • Konrad Mohrfeldt's avatar
      dx: add husky-powered pre-commit hook · 9aed3ffb
      Konrad Mohrfeldt authored
      9aed3ffb
    • Konrad Mohrfeldt's avatar
    • Konrad Mohrfeldt's avatar
      chore: add bundle size visualizer · f6c58f6d
      Konrad Mohrfeldt authored
      Sometimes it’s helpful to see which dependencies are pulled in, what’s
      pulling them in and what impact they have on the bundle size.
      rollup-plugin-visualizer does exactly that.
      f6c58f6d
    • Konrad Mohrfeldt's avatar
      chore: bump deps · c83ba187
      Konrad Mohrfeldt authored
      c83ba187
    • Konrad Mohrfeldt's avatar
      feat: migrate to fullcalender v5 · 14a9ff20
      Konrad Mohrfeldt authored
      vue-full-calendar is not the official Vue package of fullcalendar, is
      only compatible with Vue 2.x, uses the outdated fullcalendar v3 library
      and contains a bunch of huge dependencies like jQuery and moment.
      
      The changes in this commit migrate the dashboard to fullcalendar v5 and
      the official vue component. Apart from that there have been a few
      refactors and fixes. These are:
      
      * remove irrelevant stub event callbacks
      * make view updates reactive instead of imperative
        (see removal of renderView method and introduction of renderWatcher)
      * rename methods to better reflect their purpose
          resolve → enterConflictMode
          resolveEvent → resolveConflict
      * emit events in modals instead of call to methods on this.$parent
      * let → const where applicable to prevent accidental reassignments
      * switch to for-of loops (from for-in) for better readability
      * fix some typos
      
      One other major change is that timeslot and collision data is no longer
      mixed with event data for fullcalendar and is assigned to the
      extendedProps property instead. As mentioned in fullcalendars
      documentation on event parsing [1], any data that fullcalendar does not
      handle on its own is moved into the extendedProps object with the
      explicit recommendation to put them there right from the start. We
      follow that recommendation.
      
      closes #94
      
      [1] https://fullcalendar.io/docs/event-parsing
      14a9ff20
    • Konrad Mohrfeldt's avatar
      chore: simplify loops · 37fd88c5
      Konrad Mohrfeldt authored
      37fd88c5
    • Konrad Mohrfeldt's avatar
    • Konrad Mohrfeldt's avatar
      chore: fix typo · cb6b230a
      Konrad Mohrfeldt authored
      cb6b230a
  8. Nov 23, 2022
  9. Nov 18, 2022
Loading