feat: add pn ea blog#7902
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughAdds a new MDX announcement for Prisma Next Early Access (full frontmatter, technical narrative, and “Try it out”), introduces a client AutoplayYoutubeEmbed component, and registers MDX media mappings including a ChangesBlog Post: Prisma Next Early Access Announcement
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx (1)
176-176: 💤 Low valueConsider hyphenating "up-to-date" for consistency.
While "up to date" is acceptable in this predicate position, many style guides recommend hyphenating compound adjectives consistently.
📝 Suggested refinement
-Prisma Next is in Early Access and we're shipping every day, including breaking changes. To stay up to date, we ship a dedicated skill to your agent with instructions for every breaking change. +Prisma Next is in Early Access and we're shipping every day, including breaking changes. To stay up-to-date, we ship a dedicated skill to your agent with instructions for every breaking change.As per static analysis hint: "Use a hyphen to join words (QB_NEW_EN_HYPHEN)".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx` at line 176, Replace the unhyphenated phrase "up to date" in the sentence that begins "Prisma Next is in Early Access..." with the hyphenated form "up-to-date" to make the compound adjective consistent; update the string in the file's paragraph so it reads "...To stay up-to-date, we ship a dedicated skill..." (target the sentence containing "To stay up to date, we ship" in the document).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx`:
- Line 25: Replace the nonstandard compound "rampup" with the hyphenated form
"ramp-up" in the heading string "## One-line setup and onboarding. No rampup."
so the line reads "## One-line setup and onboarding. No ramp-up." and update any
identical occurrences in the same file to match standard spelling
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1).
---
Nitpick comments:
In
`@apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx`:
- Line 176: Replace the unhyphenated phrase "up to date" in the sentence that
begins "Prisma Next is in Early Access..." with the hyphenated form "up-to-date"
to make the compound adjective consistent; update the string in the file's
paragraph so it reads "...To stay up-to-date, we ship a dedicated skill..."
(target the sentence containing "To stay up to date, we ship" in the document).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: b58fef41-f1a8-4822-831b-ce48900e419d
⛔ Files ignored due to path filters (9)
apps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/ci-check.pngis excluded by!**/*.pngapps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/contract-update.mp4is excluded by!**/*.mp4apps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/migration-graph.pngis excluded by!**/*.pngapps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/migration-plan.mp4is excluded by!**/*.mp4apps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/migration-review.pngis excluded by!**/*.pngapps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/type-checked-query.mp4is excluded by!**/*.mp4apps/blog/public/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/imgs/upgrade.mp4is excluded by!**/*.mp4
📒 Files selected for processing (1)
apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx
Replace four self-hosted .mp4 videos in the Prisma Next EA blog post with unlisted YouTube iframes (autoplay, muted, looped, no controls, click-through blocked via pointer-events: none). Removes ~24 MB of binary assets from the repo. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx`:
- Around line 63-71: The iframe embeds disable user interaction via style
pointerEvents: "none" and query params controls=0, disablekb=1 and fs=0; update
each iframe (the <iframe> elements in this file) to remove pointerEvents: "none"
from the inline style and enable controls and keyboard/fullscreen by setting
controls=1 (or removing controls=0), removing disablekb=1 and fs=0 from the src
URL while keeping autoplay=1&mute=1&loop=1&playlist=..., so users can
pause/seek/enter fullscreen; apply the same change to all four video embeds
referenced in the content.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 005e0097-6a12-4832-ab4c-29708a60f6b0
📒 Files selected for processing (2)
apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdxapps/blog/src/mdx-components.tsx
✅ Files skipped from review due to trivial changes (1)
- apps/blog/src/mdx-components.tsx
- heroImagePath now points to the polished meta.png; the SVG's filter/clip-path stack rendered inconsistently in browsers. - New AutoplayYoutubeEmbed wraps each video iframe with a thumbnail overlay that fades out only once the IFrame API reports PLAYING, hiding the big center play/pause icon during the autoplay handshake. - iframe and overlay both use pointer-events: none so users cannot click through to youtube.com; videos autoplay muted and loop. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/blog/src/components/AutoplayYoutubeEmbed.tsx`:
- Line 45: The iframe in AutoplayYoutubeEmbed builds a src string that disables
user controls (const src) and the component also sets pointerEvents: "none",
preventing any interaction and violating WCAG Pause/Stop; update the src in
AutoplayYoutubeEmbed to allow user control by removing or changing the query
params that block interaction (remove controls=0, disablekb=1, fs=0 and keep
controls=1 and keyboard enabled) and remove the pointerEvents: "none" style so
users can click, pause, seek, and use keyboard controls; ensure autoplay can
remain muted if desired but the embed must permit user interaction (adjust
playlist/loop params as needed to preserve looping without disabling controls).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 1825de4a-dcfd-4657-84c5-287e604113a3
📒 Files selected for processing (3)
apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdxapps/blog/src/components/AutoplayYoutubeEmbed.tsxapps/blog/src/mdx-components.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
- apps/blog/src/mdx-components.tsx
| ); | ||
| }; | ||
|
|
||
| const src = `https://www.youtube.com/embed/${videoId}?enablejsapi=1&autoplay=1&mute=1&loop=1&playlist=${videoId}&controls=0&modestbranding=1&rel=0&showinfo=0&disablekb=1&fs=0&iv_load_policy=3&playsinline=1`; |
There was a problem hiding this comment.
Remove accessibility barriers to user control.
The iframe URL disables all user interaction (controls=0, disablekb=1, fs=0), and line 69 adds pointerEvents: "none". This completely prevents users from pausing, seeking, or controlling the video, violating WCAG 2.2.2 (Pause, Stop, Hide).
Users must be able to control auto-playing content—especially instructional demonstrations where they may need to pause and review specific steps.
♿ Proposed fix to restore user control
- const src = `https://www.youtube.com/embed/${videoId}?enablejsapi=1&autoplay=1&mute=1&loop=1&playlist=${videoId}&controls=0&modestbranding=1&rel=0&showinfo=0&disablekb=1&fs=0&iv_load_policy=3&playsinline=1`;
+ const src = `https://www.youtube.com/embed/${videoId}?enablejsapi=1&autoplay=1&mute=1&loop=1&playlist=${videoId}&controls=1&modestbranding=1&rel=0&showinfo=0&iv_load_policy=3&playsinline=1`;And remove pointer-events blocking:
style={{
position: "absolute",
inset: 0,
width: "100%",
height: "100%",
border: 0,
- pointerEvents: "none",
}}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| const src = `https://www.youtube.com/embed/${videoId}?enablejsapi=1&autoplay=1&mute=1&loop=1&playlist=${videoId}&controls=0&modestbranding=1&rel=0&showinfo=0&disablekb=1&fs=0&iv_load_policy=3&playsinline=1`; | |
| const src = `https://www.youtube.com/embed/${videoId}?enablejsapi=1&autoplay=1&mute=1&loop=1&playlist=${videoId}&controls=1&modestbranding=1&rel=0&showinfo=0&iv_load_policy=3&playsinline=1`; |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/blog/src/components/AutoplayYoutubeEmbed.tsx` at line 45, The iframe in
AutoplayYoutubeEmbed builds a src string that disables user controls (const src)
and the component also sets pointerEvents: "none", preventing any interaction
and violating WCAG Pause/Stop; update the src in AutoplayYoutubeEmbed to allow
user control by removing or changing the query params that block interaction
(remove controls=0, disablekb=1, fs=0 and keep controls=1 and keyboard enabled)
and remove the pointerEvents: "none" style so users can click, pause, seek, and
use keyboard controls; ensure autoplay can remain muted if desired but the embed
must permit user interaction (adjust playlist/loop params as needed to preserve
looping without disabling controls).
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx`:
- Line 31: The sentence currently uses the noun "setup" as a verb; change "You
can quickly setup Prisma Next..." to use the verb form "set up" so it reads "You
can quickly set up Prisma Next along with the skills and template of your choice
by running:" (update the string in the markdown content in index.mdx
accordingly).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c5f5840e-ede2-47ed-9750-fac969a4e7a0
📒 Files selected for processing (1)
apps/blog/content/blog/prisma-next-early-access-write-your-contract-prompt-your-agent-ship-your-app/index.mdx
…tract-prompt-your-agent-ship-your-app/index.mdx
…tract-prompt-your-agent-ship-your-app/index.mdx
…tract-prompt-your-agent-ship-your-app/index.mdx
sneub
left a comment
There was a problem hiding this comment.
It's already great! I have a few comments that may help make it clearer
|
|
||
| Today, **Prisma Next is open for Early Access for Postgres and [MongoDB](https://www.prisma.io/blog/mongodb-without-compromise).** | ||
|
|
||
| ## One-line setup and onboarding. No ramp-up. |
There was a problem hiding this comment.
"Learning curve" would be more immediately understandable. Ramp up feels ambiguous, not necessarily talking about your understanding/confidence in the topic
…tract-prompt-your-agent-ship-your-app/index.mdx
Summary by CodeRabbit