Don’t set a “day-height” and it will auto-expand, otherwise it will use day-height value.

I see - not sure if it’d compete with QEditor. Possibly not as that is not markup/markdown

@digiproduct
What do you mean with “markup editor with icons”? Throw me the pitch…

https://github.com/quasarframework/app-extension-qcalendar/releases/tag/v1.0.0-alpha.5

• feat(day-height): Auto-expanding day height (month view)

Yes, you can easily change it. I change it when I use it for my documentation for QMarkdown itself! The whole point was to do markdown, but follow BEM naming to make it very easy to modify. You don’t everyone having the same look-and-feel

I suggest using boot files to import your “common boot files”

@digiproduct No, I don’t think it’d happen. We don’t want to bloat the core with heavy components.

@digiproduct Already is… https://v1.quasar-framework.org/app-extensions/discover

@Patrick-Spiegel
I find I get a way better user experience for a Quasar project to use the Quasar CLI. It wouldn’t even cross my mind to deprecate to the Vue CLI.

https://github.com/quasarframework/app-extension-qcalendar/releases/tag/v1.0.0-alpha.4
update dependenices

• fix(css): shift q-calendar-weekly__day-label so it’s not on border
• fix: validation for ‘now’ prop
• fix(css): .q-calendar-weekly__day-month position
• fix(css): .q-calendar-weekly__day-month–day-of-year position
• fix(css): q-calendar-daily__head-day.q-outside color
• fix(css): q-calendar-daily__head-day.q-current-day.q-calendar-daily__head-day-label color, border, and font-weight
• fix(css): q-calendar-daily__head-day.q-future-day.q-calendar-daily__head-day-label color