pn-new-crm

letsbe/pn-new-crm

Fork 0

Commit Graph

Author	SHA1	Message	Date
Matt Ciaccio	3f6a8aa3b8	feat(bulk): synchronous bulk action endpoints + UI on interests/clients/yachts Until now the only bulk action anywhere was Archive on the interests list — implemented as parallel fan-out with no per-row failure reporting. The bulk BullMQ worker was a TODO stub with no producers. - bulk-helpers.runBulk wraps a per-row loop and returns {results, summary} for the caller. Page-size capped at 100. - New endpoints: /api/v1/{interests,clients,yachts,companies}/bulk with a Zod discriminated union over the action. Interests support change_stage + add_tag + remove_tag + archive; clients/yachts/companies support archive + add_tag + remove_tag. Each action is permission-gated individually (delete vs edit vs change_stage). - interest-list, client-list, yacht-list expose the new actions in the bulk-action toolbar with dialogs for stage / tag selection. Failure summaries surface via window.confirm. - bulkWorker stub gets a docblock explaining the v1 sync-only choice and what the queue is reserved for (CSV imports, port-wide migrations, bulk emails to >100 recipients). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-06 14:58:34 +02:00
Matt	67d7e6e3d5	Initial commit: Port Nimara CRM (Layers 0-4) Some checks failed Build & Push Docker Images / build-and-push (push) Has been cancelled Details Build & Push Docker Images / deploy (push) Has been cancelled Details Build & Push Docker Images / lint (push) Has been cancelled Details Full CRM rebuild with Next.js 15, TypeScript, Tailwind, Drizzle ORM, PostgreSQL, Redis, BullMQ, MinIO, and Socket.io. Includes 461 source files covering clients, berths, interests/pipeline, documents/EOI, expenses/invoices, email, notifications, dashboard, admin, and client portal. CI/CD via Gitea Actions with Docker builds. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-03-26 11:52:51 +01:00

Author

SHA1

Message

Date

Matt Ciaccio

3f6a8aa3b8

feat(bulk): synchronous bulk action endpoints + UI on interests/clients/yachts

Until now the only bulk action anywhere was Archive on the interests
list — implemented as parallel fan-out with no per-row failure
reporting. The bulk BullMQ worker was a TODO stub with no producers.

- bulk-helpers.runBulk wraps a per-row loop and returns
  {results, summary} for the caller. Page-size capped at 100.
- New endpoints: /api/v1/{interests,clients,yachts,companies}/bulk
  with a Zod discriminated union over the action. Interests support
  change_stage + add_tag + remove_tag + archive; clients/yachts/companies
  support archive + add_tag + remove_tag. Each action is permission-gated
  individually (delete vs edit vs change_stage).
- interest-list, client-list, yacht-list expose the new actions in the
  bulk-action toolbar with dialogs for stage / tag selection. Failure
  summaries surface via window.confirm.
- bulkWorker stub gets a docblock explaining the v1 sync-only choice
  and what the queue is reserved for (CSV imports, port-wide migrations,
  bulk emails to >100 recipients).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-06 14:58:34 +02:00

Matt

67d7e6e3d5

Initial commit: Port Nimara CRM (Layers 0-4)

Build & Push Docker Images / build-and-push (push) Has been cancelled

Details

Build & Push Docker Images / deploy (push) Has been cancelled

Details

Build & Push Docker Images / lint (push) Has been cancelled

Details

Full CRM rebuild with Next.js 15, TypeScript, Tailwind, Drizzle ORM,
PostgreSQL, Redis, BullMQ, MinIO, and Socket.io. Includes 461 source
files covering clients, berths, interests/pipeline, documents/EOI,
expenses/invoices, email, notifications, dashboard, admin, and
client portal. CI/CD via Gitea Actions with Docker builds.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-26 11:52:51 +01:00

2 Commits