[Plugin] calendar

Open Beginner friendly
#228 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go, next.js, react, typescript, vite

Research direction

Start with the plugin manifest and README for grit-calendar to see how it targets triple projects with Next.js and Vite/TanStack admins. Review the reported install and removal behavior, then verify the feature works on both admin shapes; the issue says CI already covers scaffold, type-check, tests, removal, and API build. The plugin is already published at v0.5.0, so check the repository for a specific follow-up task before taking this issue on.

Written by the indexing model from the issue text.

Description

Plugin name

calendar

Repository

github.com/daljo25/grit-calendar

One line

Monthly, weekly, daily and lane views for any resource with a date field, plus a dashboard widget

Architectures it works on

triple

On a freshly scaffolded project
  • grit plugin add <repo> installs without errors
  • go build ./... compiles afterwards
  • grit plugin remove <name> leaves the project compiling again
  • It declares its dependencies rather than assuming the project has them
  • Every file it writes is one it created, so removal deletes nothing it did not add
What it writes

On a triple + Vite/TanStack project, 9 files and 9 patches:

Installing calendar v0.5.0

  ✓ apps/admin/src/components/calendar/calendar-create-intent.tsx
  ✓ apps/admin/src/components/calendar/calendar-data.ts
  ✓ apps/admin/src/components/calendar/calendar-event-form.tsx
  ✓ apps/admin/src/components/calendar/calendar-view.tsx
  ✓ apps/admin/src/components/calendar/calendar-widget.tsx
  ✓ apps/admin/src/components/calendar/calendar.css
  ✓ apps/admin/src/config/calendar.ts
  ✓ apps/admin/src/routes/_dashboard/calendar.tsx
  ✓ apps/admin/src/routes/_dashboard/calendar/$id.tsx
  ✓ patched apps/admin/src/components/chrome/CollapsibleSidebar.tsx
  ✓ patched apps/admin/src/lib/icons.ts
  ✓ patched apps/admin/src/lib/icons.ts
  ✓ patched apps/admin/src/lib/dashboard-catalog.ts
  ✓ patched apps/admin/src/pages/dashboard.tsx
  ✓ patched apps/admin/src/pages/dashboard.tsx
  ✓ patched apps/admin/src/components/resource/resource-page.tsx
  ✓ patched apps/admin/src/components/resource/resource-page.tsx
  ✓ patched apps/admin/src/components/chrome/CollapsibleSidebar.tsx

  ✅ calendar installed (9 files, 9 patches)

On a triple + Next.js project, the same set under apps/admin/ without the src/ segment, plus three component tests in apps/admin/__tests__/ and the two route files under app/(dashboard)/calendar/: 12 files and 9 patches.

The patches add the sidebar entry, two icon keys in lib/icons.ts, the dashboard widget, and a small bridge in the resource page so ?action=create opens the resource's own create sheet.

Anything a reviewer should know

MIT licensed. calendarkit-pro is pinned to the exact version 2.0.0 rather than a caret range: two CSS rules that hide the library's floating Create button and its context-menu Delete depend on that release's class names, and a minor bump could un-hide both.

Only triple projects are supported, in both admin shapes (Next.js and Vite/TanStack). A community manifest has no admin-root placeholder, so double, single, API-only and mobile projects get nothing: the plugin writes no files there rather than half-installing. That is grit#227, and it is documented in the README as pending.

The UI strings are English. No Grit plugin ships translations yet, and i18n is planned for a later version.

CI is public and green on the v0.5.0 tag: it scaffolds triple Next, triple Vite and API-only projects, installs the plugin, type-checks both admins, runs both admins' test suites, then removes the plugin and builds the API again. https://github.com/daljo25/grit-calendar/actions

Dominant language
Go
Stars
152
Forks
20
Avg merge
1d 49m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MUKE-coder/grit

All issues in MUKE-coder/grit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.