feat(image): honor alignment + surface display size for migrated images (#1404)#1406
Conversation
…-cms#1404 render follow-up) Renders the real RAFYC image node through astro-portabletext via the production dispatch (type.image -> Image.astro), default vs delegating override vs no-locals. All three emit a valid src: the override receives the full node intact and delegation to <Image> does NOT render empty. Confirms alignment is dropped.
…d images (emdash-cms#1404) Renderer (core/Image.astro): add alignment to the PT image node props and emit an emdash-image--align-{left,right,center,wide,full} figure class with default CSS (floats wrap text; wide/full span the column). Editor (admin): thread alignment through the PortableText<->TipTap serializer (both directions), the TipTap image node attribute/commands, and add an alignment selector to ImageDetailPanel. Also relax the Display Size gate from (width && height) to (src) so migrated WordPress images, which carry only displayWidth/displayHeight and no original dims, can still be resized; the aspect-ratio lock and reset-to-original now degrade gracefully when originals are unknown. Repro test asserts the renderer now emits the alignment class.
Float left/right (text wraps) and size center/wide/full in the TipTap image NodeView so the editor preview matches the published <Image> output.
🦋 Changeset detectedLatest commit: f681393 The changes in this PR will be included in the next version bump. This PR includes changesets to release 14 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
Add a max-width:640px media query so left/right-aligned images drop to full-width blocks on phones instead of staying floated and cramped.
Overlapping PRsThis PR modifies files that are also changed by other open PRs:
This may cause merge conflicts or duplicated work. A maintainer will coordinate. |
Heads-up on the overlap noticeI checked the files this PR shares with the other open image PRs flagged by the overlap bot:
The three PRs are additive and orthogonal — each threads a different image attribute ( The one spot needing a deliberate (but compatible) resolution is the Merge-order preference: happy to go in whatever order suits maintainers, but this one is the smallest and is green/review-ready, so merging it first would let #704/#143 rebase trivially. If #143 lands first instead, I'll fold |
@emdash-cms/admin
@emdash-cms/auth
@emdash-cms/auth-atproto
@emdash-cms/blocks
@emdash-cms/cloudflare
@emdash-cms/contentful-to-portable-text
emdash
create-emdash
@emdash-cms/gutenberg-to-portable-text
@emdash-cms/plugin-cli
@emdash-cms/plugin-types
@emdash-cms/registry-client
@emdash-cms/registry-lexicons
@emdash-cms/sandbox-workerd
@emdash-cms/x402
@emdash-cms/plugin-ai-moderation
@emdash-cms/plugin-atproto
@emdash-cms/plugin-audit-log
@emdash-cms/plugin-color
@emdash-cms/plugin-embeds
@emdash-cms/plugin-field-kit
@emdash-cms/plugin-forms
@emdash-cms/plugin-webhook-notifier
commit: |
ascorbic
left a comment
There was a problem hiding this comment.
Overall good, but the tests need soem cleanup
| @@ -0,0 +1,61 @@ | |||
| /** | |||
There was a problem hiding this comment.
This file isn't testing anything real: it's just testing its own local implementations. Delete it: the other test file has the real tests.
There was a problem hiding this comment.
Done in c4dfd14 — deleted. The real coverage lives in image-render.render.test.ts.
| @@ -0,0 +1,70 @@ | |||
| import { PortableText } from "astro-portabletext"; | |||
| /** | |||
| * Faithful container render for the #1404 follow-up. | |||
There was a problem hiding this comment.
| * Faithful container render for the #1404 follow-up. |
There was a problem hiding this comment.
Done in c4dfd14 — dropped that header line.
| const imgSrc = (html: string) => html.match(/<img[^>]*\bsrc="([^"]*)"/)?.[1] ?? "(no <img>)"; | ||
|
|
||
| describe("faithful render of migrated image node", () => { | ||
| test("1. default type.image=Image.astro", async () => { |
There was a problem hiding this comment.
Done in c4dfd14 — removed the 1./2./3. prefixes.
| @@ -0,0 +1,24 @@ | |||
| import { getViteConfig } from "astro/config"; | |||
There was a problem hiding this comment.
Is this file used anywhere? It looks like nothing is running these tests
There was a problem hiding this comment.
It is now — that comment predates the wiring. The render tests need the Astro Vite plugin, so they can't run under the plain-node test:unit config (sweeping them in there broke the whole core suite at collection time). They're now run via a dedicated test:repro script (packages/core/package.json, mirroring test:smoke/test:integration), and CI invokes the config right after test:unit in the Tests job (.github/workflows/ci.yml). The plain-node config also excludes **/*.render.test.ts so it won't re-collect them.
The emdash-cms#1404 follow-up added tests/repro/*.render.test.ts (which import .astro components) plus vitest.repro.config.ts (Astro Vite plugin), but never wired the runner up. The default vitest.config.ts swept the render test into its plain-node run, which cannot transform .astro, so the whole core suite failed to load (0 tests collected). - vitest.config.ts: exclude tests/repro/**/*.render.test.ts (needs Astro) - package.json: add test:repro script (mirrors test:smoke/test:integration) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
5c26f31 split the Astro render test out of the plain-node test:unit run (vitest.repro.config.ts + test:repro script) but the CI invocation was never committed, so the emdash-cms#1404 alignment/display-size render coverage would not execute in CI. Run the repro config right after test:unit in the Tests job. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reconcile emdash-cms#1404 alignment/display-size work with the emdash-cms#1424 Image.astro responsive-image refactor (getImage + media/responsive.js) on main.
Per @ascorbic review on emdash-cms#1406: - delete tests/repro/image-render.test.ts: it only exercised local reimplementations (buildRenderMediaUrl), not the real component; the real coverage lives in image-render.render.test.ts. - strip the 1./2./3. numbering from the render test titles. - drop the throwaway emdash-cms#1404-follow-up header line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Thanks @ascorbic — review feedback addressed in c4dfd14:
Also rebased onto |
What does this PR do?
The Gutenberg to Portable Text importer captures WordPress image
alignmenton the image node, but it was dropped at render and not editable. This wires it through end to end and surfaces the existing display-size controls for migrated images.packages/core/src/components/Image.astro): emitemdash-image--align-{left,right,center,wide,full}from the nodesalignment`, with default CSS (left/right float and wrap text; center centers; wide/full span the column).packages/admin): threadalignmentthrough the PortableText/TipTap serializer (both directions) and the TipTap image node; add an Alignment selector toImageDetailPanel; reflect alignment in the image NodeView so the editor preview matches the published output.width && heighttosrcso WordPress-imported images (which carry onlydisplayWidth/displayHeight, no originals) are resizable; the aspect-ratio lock and reset-to-original degrade gracefully when originals are unknown.Validated end to end on a real WordPress-migrated site: editor -> save -> published page all agree on the canonical
alignmentfield.Closes #1404
Type of change
Checklist
pnpm typecheckpassespnpm lintpassespnpm testpasses (or targeted tests for my change)pnpm formathas been runAI-generated code disclosure
Screenshots / test output
Container-render repro asserts the alignment class is emitted (default render and via a delegating component override); validated end to end on a live WordPress-migrated site (editor -> save -> published render).