QRun-IO/qbit-collaboration
3
0 Fork 0
Code Issues 3 Pull Requests 10 Actions Packages Projects Releases 6 Wiki Activity

refactor(email): use qbit-email's public api package; no G1 allow-list #19

Merged
KofTwentyTwo merged 1 commits from feature/email-api into develop 2026-10-14 15:25:08 +00:00
Conversation 0 Commits 1 Files Changed 6
+53 -40
KofTwentyTwo commented 2026-10-14 15:20:39 +00:00 (Migrated from github.com)
Copy link
Copy source

Follow-up to QRun-IO/qbit-marketing#13 (cross-qbit imports of qbit-email internals).

  • Every qbit-email reference now goes through the published com.kingsrook.qbits.email.api (EmailApi, EmailApiRequest, EmailApiResult, EmailApiTemplate, ...) in qbit-email 0.1.0-RC.2 from Central. Behaviour is identical: same templates, categories, idempotency keys, linked records and status mapping. Tests use the producer and config only to set up the host instance.
  • qbit-build-parent 2.1.1: its default G1 allow-lists include qbit-email's API (QRun-IO/qbit-bom#12), so the per-repo qbit.guardrails.allowed* properties are removed.
  • ./mvnw verify green against Central's RC.2 and parent 2.1.1, guardrails on.

Next step once a QQQ RC carries QRun-IO/qqq#1194: send-only paths move to core SendMessageAction with provider qbitEmail, and the api package stays only for lookups.

🤖 Generated with Claude Code

Follow-up to QRun-IO/qbit-marketing#13 (cross-qbit imports of qbit-email internals). - Every qbit-email reference now goes through the published `com.kingsrook.qbits.email.api` (`EmailApi`, `EmailApiRequest`, `EmailApiResult`, `EmailApiTemplate`, ...) in qbit-email **0.1.0-RC.2** from Central. Behaviour is identical: same templates, categories, idempotency keys, linked records and status mapping. Tests use the producer and config only to set up the host instance. - **qbit-build-parent 2.1.1**: its default G1 allow-lists include qbit-email's API (QRun-IO/qbit-bom#12), so the per-repo `qbit.guardrails.allowed*` properties are removed. - `./mvnw verify` green against Central's RC.2 and parent 2.1.1, guardrails on. Next step once a QQQ RC carries QRun-IO/qqq#1194: send-only paths move to core `SendMessageAction` with provider `qbitEmail`, and the api package stays only for lookups. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
Architecture review: coupling, cohesion, UI API
 bug
Something isn't working
 dependencies
documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 java
Pull requests that update java code
 question
Further information is requested
 secuurity
wontfix
This will not be worked on
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-collaboration#19