Skip to content

fix(marketing): register mailTransport so the deliverability panel can read it - #1803

Merged
rubenvdlinde merged 1 commit into
developmentfrom
fix/mail-transport-object-type
Sep 5, 2026
Merged

fix(marketing): register mailTransport so the deliverability panel can read it#1803
rubenvdlinde merged 1 commit into
developmentfrom
fix/mail-transport-object-type

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What

The deliverability panel asked the object store for mailTransport rows and the store never issued a request. src/config/objectTypes.js is what fetchCollection resolves a type against, and mailTransport was the one schema in the app that a component reads this way without being listed there.

Every tenant saw "No mail transports configured yet" next to three seeded transports, including the instance mail server every install gets for free. The objects were correct the whole time; nothing ever asked for them.

The wizard test deep-linked with a #/blasts/new hash though the app is path-routed, so it asserted against the dashboard rather than the wizard.

How it was found, and what else was checked

Playwright against the merged tree. I then swept every fetchCollection('…') call in src/ against the registered slugs: mailTransport is the only one missing, so this is a single gap rather than a pattern.

Verification, by exit code

composer check:strict 0 · npm run format 0 · lint 0 · test:unit 0 · check:manifest 0 · check:spec-links 0 · check:schema-l10n 0 · check:l10n-js 0 · hydra gates with HYDRA_GATE_BASE_REF=origin/development, full scope: 0, 77 of 77 applicable gates ran.

Playwright: marketing-transports 2/2, both previously failing. Confirmed in a browser before and after: the panel now lists the instance mail server with its SPF, DKIM and DMARC state.

🤖 Generated with Claude Code

…n read it

The panel asked the object store for mailTransport rows and the store
never issued a request: src/config/objectTypes.js is what fetchCollection
resolves a type against, and mailTransport was the one schema in the app
that a component reads this way without being listed there. Every tenant
saw "No mail transports configured yet" beside three seeded transports,
including the instance mail server every install gets for free.

The wizard test deep-linked with a '#/blasts/new' hash though the app is
path-routed, so it asserted against the dashboard.
@rubenvdlinde
rubenvdlinde merged commit 44b7684 into development Sep 5, 2026
35 checks passed
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/pipelinq @ 72b4fb7

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
check-vue-demi
test-l10n
format
check-schema-l10n
check-l10n-js
composer ✅ 106/106
npm ✅ 637/637
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates

Quality workflow — 2026-09-05 12:03 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant