@meith/plugin-calendar 0.31.0 → 0.33.0

package/README.md

@@ -34,11 +34,18 @@ every signed-in member; guests never may.
 
 Removing an event is allowed to whoever added it, and to any organiser.
 
-This is a roster rather than a usergroup on purpose. `@meith/plugin-kit`
-gives a plugin no way to read a member's groups, and the board's own guard
-says why: group membership is the Authorizer's business, and a plugin never
-gets an `Actor` to ask with. A roster the plugin owns keeps the decision
-inside the plugin's own surface, where it belongs.
+This is a roster rather than a usergroup, and the roster is what this plugin
+ships with. It keeps the decision inside the plugin's own surface, where a
+plugin never gets an `Actor` and cannot see a member's groups at large.
+
+There is now an alternative for a board that would rather run its organisers
+as a usergroup. `context.grants.holds(userId, groupKey)` reads whether a
+member holds a group, but only one the operator has marked **"may be granted
+by plugins"** — the same opt-in the write side needs, and the same privacy
+line: every other group stays invisible. A board could mark an
+`organisers` group grantable and ask `holds` instead of consulting the
+roster. Doing that migration is not part of this plugin as shipped; the
+roster remains the default, and the choice is the operator's.
 
 In the downloaded `.ics`, the event's own link becomes the calendar entry's
 `URL` — it is the one a reader wants to act on from their calendar app — and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meith/plugin-calendar",
-  "version": "0.31.0",
+  "version": "0.33.0",
   "description": "A shared calendar: events the community can see, linked to the threads that discuss them.",
   "license": "MIT",
   "repository": {
@@ -20,7 +20,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@meith/plugin-kit": "^0.31.0"
+    "@meith/plugin-kit": "^0.33.0"
   },
   "peerDependencies": {
     "react": "^19.2.0"

package/src/definition.tsx

@@ -20,7 +20,7 @@ export const calendarPlugin = definePlugin({
   key: 'calendar',
   name: en['calendar.definition.name'],
   nameKey: 'calendar.definition.name',
-  version: '0.31.0',
+  version: '0.33.0',
   description: en['calendar.definition.description'],
   descriptionKey: 'calendar.definition.description',
   apiVersion: '0',

package/src/ui/thread-card.tsx

@@ -5,6 +5,10 @@ import en from '../messages/en.json'
 import { eventsForThread } from '../store'
 import { EventLink } from './event-link'
 
+function translated(context: PluginRegionContext, key: keyof typeof en): string {
+  return context.t.has(key) ? context.t.t(key) : en[key]
+}
+
 export async function ThreadEventCard(context: PluginRegionContext) {
   if (context.subjectId === null) return null
 
@@ -21,16 +25,16 @@ export async function ThreadEventCard(context: PluginRegionContext) {
   return (
     <section className="rounded-md border border-border bg-card p-3 text-sm" data-plugin="calendar">
       <p className="text-xs uppercase tracking-wide text-muted-foreground">
-        {en['calendar.thread.card']}
+        {translated(context, 'calendar.thread.card')}
       </p>
       <p className="font-semibold">{event.title}</p>
       <p className="text-muted-foreground">
         <time dateTime={event.startsAt.toISOString()}>
-          {formatRange(event.startsAt, event.endsAt)}
+          {formatRange(event.startsAt, event.endsAt, context.locale)}
         </time>
         {event.location !== '' && <span> · {event.location}</span>}
       </p>
-      <EventLink event={event} label={en['calendar.event.linkFallback']} />
+      <EventLink event={event} label={translated(context, 'calendar.event.linkFallback')} />
     </section>
   )
 }