Open
Conversation
- oxfmt ^0.33.0 → ^0.46.0 - oxlint ^1.48.0 → ^1.61.0 - add **/public/** to ignorePatterns in .oxfmtrc.json and .oxlintrc.json
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughConfiguration updates extend ignore patterns for formatter and linter. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
AmanVarshney01
changed the title
Contributor
🍈 Lychee Link Check Report3756 links: ❌ Errors
Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
oxfmt 0.46 mis-indents closing JSX tags (</Accordion>, </Accordions>) when they follow markdown list items, and has acorn regex parse bugs on two files, both of which break MDX compilation.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
apps/blog/content/blog/e2e-type-safety-graphql-react-1-I2GxIfxkSZ/index.mdx (1)
439-443:⚠️ Potential issue | 🟡 MinorStray
difftext inside TSX examples should be removedLine 439 and Line 507 include raw
difflines insidetsxsnippets. That looks like patch metadata leakage and makes the examples confusing/non-runnable.Suggested fix
```tsx -diff // src/components/UserDisplay.tsx +import MessageDisplay from './MessageDisplay'```tsx -diff // src/components/MessageDisplay.tsx import { Message } from '../types' +import Branch from './Branch'Also applies to: 507-512
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/e2e-type-safety-graphql-react-1-I2GxIfxkSZ/index.mdx` around lines 439 - 443, Remove the stray "diff" lines that leaked into the TSX example code blocks for the components (the snippets showing "// src/components/UserDisplay.tsx" and "// src/components/MessageDisplay.tsx"); edit the MDX so the code blocks contain only valid TSX (keep the import lines like "import MessageDisplay from './MessageDisplay'" and "import Branch from './Branch'" but delete the leading "diff" tokens), then preview the MDX to ensure the UserDisplay and MessageDisplay examples render as runnable TSX without patch metadata.apps/blog/content/blog/convergence/index.mdx (1)
272-272:⚠️ Potential issue | 🟡 MinorCorrect spelling error.
"acros" should be "across".
📝 Proposed fix
-1. **Migrations need specialized attention**: The 9k test suite isn't overkill, it's the cost of reliability acros databases +1. **Migrations need specialized attention**: The 9k test suite isn't overkill, it's the cost of reliability across databases🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 272, The sentence in the list item starting with "1. **Migrations need specialized attention**" contains a typo: replace the misspelled word "acros" with "across" so the sentence reads "The 9k test suite isn't overkill, it's the cost of reliability across databases."apps/blog/content/blog/fullstack-nextjs-graphql-prisma-oklidw1rhw/index.mdx (1)
383-423:⚠️ Potential issue | 🟡 MinorMove the
copydirective to the opening fence line.Line 384 has the
copydirective on a separate line inside the code block. It should be on the same line as the opening fence:```prisma copyrather than```prismafollowed bycopyon the next line.When
copyappears inside the code block instead of as a modifier to the fence, it renders as literal text in the output rather than functioning as a copy-to-clipboard directive. Other Prisma tutorial files in the same directory (e.g.,database-access-on-the-edge-8F0t1s1BqOJE/index.mdx) correctly place the directive on the fence line itself.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/fullstack-nextjs-graphql-prisma-oklidw1rhw/index.mdx` around lines 383 - 423, In the Prisma schema code block that currently starts with "```prisma" and has a standalone "copy" on the next line, move the copy directive onto the opening fence so the fence reads "```prisma copy" (i.e., combine the language and the copy modifier on the same opening fence for the Prisma schema code block that contains the User, Role, and Link models).apps/blog/content/blog/fullstack-nextjs-graphql-prisma-3-clxbrcqppv/index.mdx (1)
583-599:⚠️ Potential issue | 🟡 MinorUse correct syntax highlighting for diff blocks.
The code block at line 583 is marked as
ts(TypeScript) but contains diff syntax with the+prefix. Additionally, thediff;line is extraneous—it appears to be an attempted annotation that doesn't belong in the code.The code block should use the
difflanguage identifier instead ofts, which will properly render the diff syntax highlighting. Remove the unnecessarydiff;line from the content.Suggested fix
-```ts -diff; +```diff // graphql/builder.ts // ...code above remains unchanged builder.queryType({🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/fullstack-nextjs-graphql-prisma-3-clxbrcqppv/index.mdx` around lines 583 - 599, The fenced code block in the MDX shows a TypeScript fence with an extraneous "diff;" token and a diff-style "+builder.mutationType({})" line; update the fence language from "ts" to "diff" and remove the stray "diff;" line so the block correctly renders diff syntax and the added line (+builder.mutationType({})) is highlighted; locate the block around the builder.queryType(...) and builder.mutationType symbols to apply this change.
🟡 Minor comments (33)
apps/blog/content/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres/index.mdx-44-44 (1)
44-44:⚠️ Potential issue | 🟡 MinorHyphenate compound adjective for correctness and readability
On Line 44, change “vibe coded apps” to “vibe-coded apps” for standard English compound-modifier usage.
Suggested edit
-While vibe coded apps don't yet cross the threshold of complexity required for serious application development, the wider trend of AI-assisted coding is certainly reshaping the software development industry! Repetitive and monotonous coding tasks, features with very detailed specifications and prototyping are areas that are seeing major productivity boosts by AI and let developers build applications at new speed levels. +While vibe-coded apps don't yet cross the threshold of complexity required for serious application development, the wider trend of AI-assisted coding is certainly reshaping the software development industry! Repetitive and monotonous coding tasks, features with very detailed specifications and prototyping are areas that are seeing major productivity boosts by AI and let developers build applications at new speed levels.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres/index.mdx` at line 44, Replace the unhyphenated phrase "vibe coded apps" with the compound adjective "vibe-coded apps" in the MDX content (the sentence beginning "While vibe coded apps...") so the compound modifier is hyphenated for correctness and readability.apps/blog/content/blog/backend-prisma-typescript-orm-with-postgresql-rest-api-validation-dcba1ps7kip3/index.mdx-797-797 (1)
797-797:⚠️ Potential issue | 🟡 MinorFix the misspellings in this sentence.
There are three typos here:
happpy→happy,sucessfully→successfully, andommitting→omitting.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/backend-prisma-typescript-orm-with-postgresql-rest-api-validation-dcba1ps7kip3/index.mdx` at line 797, Fix the three typos in the sentence that explains the new test: change "happpy" to "happy", "sucessfully" to "successfully", and "ommitting" to "omitting" in the paragraph that starts "Now that you've written a test for the ...", ensuring the corrected sentence reads "...happy path (creating a user successfully)... omitting the required field `firstName`...".apps/blog/content/blog/elsevier-customer-story-SsAASKagMHtN/index.mdx-62-62 (1)
62-62:⚠️ Potential issue | 🟡 MinorFix sentence grammar in the Prisma Migrate paragraph.
This line currently reads awkwardly and is grammatically broken (
...migrations gave Serghei...). Also, use “hassle-free” with a hyphen.✍️ Proposed copy edit
-The team desired to focus on speaking to users every day to understand what their needs were and what features were the highest priorities for the MVP. Serghei used [Prisma Migrate](https://www.prisma.io/migrate) to automatically generate fully customizable database schema migrations gave Serghei the confidence to be able to implement changes quickly and hassle free. +The team desired to focus on speaking to users every day to understand their needs and which features were the highest priorities for the MVP. Serghei used [Prisma Migrate](https://www.prisma.io/migrate) to automatically generate fully customizable database schema migrations, which gave him the confidence to implement changes quickly and hassle-free.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/elsevier-customer-story-SsAASKagMHtN/index.mdx` at line 62, Fix the broken sentence in the "Prisma Migrate" paragraph: reword the sentence that currently reads "...migrations gave Serghei the confidence to be able to implement changes quickly and hassle free" so it reads smoothly and grammatically (for example: "Serghei used Prisma Migrate to automatically generate fully customizable database schema migrations, which gave him the confidence to implement changes quickly and hassle-free."), and ensure "hassle-free" is hyphenated; update the paragraph in the elsevier-customer-story-SsAASKagMHtN index.mdx content where Prisma Migrate is mentioned.apps/blog/content/blog/how-migrating-from-Sequelize-to-Prisma-allowed-Invisible-to-scale-i4pz2mwu6q/index.mdx-144-144 (1)
144-144:⚠️ Potential issue | 🟡 MinorFix hyphenation in “single-handedly”.
Line 144 uses “single handedly”; this should be “single-handedly” for correct grammar in published content.
✍️ Proposed fix
-This is especially evident when looking at Pieter’s work: Pieter single handedly assessed the flaws in the previous stack and took ownership of designing a new, scalable and future-proof solution. +This is especially evident when looking at Pieter’s work: Pieter single-handedly assessed the flaws in the previous stack and took ownership of designing a new, scalable and future-proof solution.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/how-migrating-from-Sequelize-to-Prisma-allowed-Invisible-to-scale-i4pz2mwu6q/index.mdx` at line 144, Replace the incorrect phrase in the sentence containing "Pieter single handedly assessed the flaws..." by hyphenating "single-handedly"; update the text in the paragraph that currently reads "Pieter single handedly assessed the flaws in the previous stack and took ownership of designing a new, scalable and future-proof solution." to "Pieter single-handedly assessed the flaws in the previous stack and took ownership of designing a new, scalable and future-proof solution."apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx-21-23 (1)
21-23:⚠️ Potential issue | 🟡 MinorFix spelling and brand-style consistency in this paragraph.
There are a couple of copy issues in user-facing text:
- Line 21:
continuosly→continuously- Line 23:
Stackoverflow→Stack Overflow✍️ Suggested copy fix
-We're continuosly amazed by the awesome content produced by the [Prisma community](https://www.prisma.io/community), be it in the form of example projects, video tutorials or blog articles! +We're continuously amazed by the awesome content produced by the [Prisma community](https://www.prisma.io/community), be it in the form of example projects, video tutorials or blog articles! -Not to mention how community members support each other in [GitHub Discussions](https://github.com/prisma/prisma/discussions) and on [Stackoverflow](https://stackoverflow.com/questions/tagged/prisma) or have lively discussions and show off their Prisma projects on [Slack](https://slack.prisma.io) (join the [`#showcase`](https://app.slack.com/client/T0MQBS8JG/C565176N6) channel to learn more). +Not to mention how community members support each other in [GitHub Discussions](https://github.com/prisma/prisma/discussions) and on [Stack Overflow](https://stackoverflow.com/questions/tagged/prisma) or have lively discussions and show off their Prisma projects on [Slack](https://slack.prisma.io) (join the [`#showcase`](https://app.slack.com/client/T0MQBS8JG/C565176N6) channel to learn more).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx` around lines 21 - 23, Update the user-facing paragraph in the MDX content to fix spelling and brand-style: change "continuosly" to "continuously" and change "Stackoverflow" to the brand-correct "Stack Overflow" in the sentence that mentions community support and sites (the paragraph in apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx mentioning Prisma community, GitHub Discussions, Stack Overflow and Slack/#showcase).apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx-45-45 (1)
45-45:⚠️ Potential issue | 🟡 MinorCorrect hyphenation and spelling in the emphasized sentence.
Line 45 has two text issues:
peer to peershould bepeer-to-peer, andinfluencialshould beinfluential.✍️ Suggested copy fix
-However, ultimately, **peer to peer feedback is indeed the most influencial approach there is**, and we want to reward those contributors who help spread the word about Prisma. +However, ultimately, **peer-to-peer feedback is indeed the most influential approach there is**, and we want to reward those contributors who help spread the word about Prisma.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/ambassador-program-nxkWGcGNuvFx/index.mdx` at line 45, Fix the typos in the emphasized sentence "**peer to peer feedback is indeed the most influencial approach there is**": change "peer to peer" to "peer-to-peer" and correct "influencial" to "influential", preserving the surrounding emphasis markup and punctuation.apps/blog/content/blog/esop-exercise-windows/index.mdx-78-78 (1)
78-78:⚠️ Potential issue | 🟡 MinorUse one spelling variant consistently (
modelingvsmodelling).Line 78 uses “modeling” while earlier text uses “modelling.” Please standardize to one variant for editorial consistency.
✏️ Proposed wording fix
-Ultimately, the idea is not to try and engage in detailed financial modeling but rather to implement an approach that approximates future expectations and changes over time as more information becomes available. +Ultimately, the idea is not to try and engage in detailed financial modelling but rather to implement an approach that approximates future expectations and changes over time as more information becomes available.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/esop-exercise-windows/index.mdx` at line 78, Line 78 uses the American spelling "modeling" while earlier text uses "modelling"; update the phrase "detailed financial modeling" to "detailed financial modelling" and scan the rest of the document for any other instances of "modeling" to make all occurrences match the chosen variant ("modelling") for consistent spelling across the article.apps/blog/content/blog/helping-rapha-access-data-across-platforms-n3jfhtyu6rgn/index.mdx-65-65 (1)
65-65:⚠️ Potential issue | 🟡 MinorUse a consistent pronoun in this sentence.
“help them develop its GraphQL API” reads inconsistently; “their” is clearer.
✏️ Suggested copy fix
-Rapha's mobile team uses Prisma to help them develop its GraphQL API for their PostgreSQL data. This API is then served by Apollo server and consumed by both their iOS and Android applications. +Rapha's mobile team uses Prisma to help them develop their GraphQL API for their PostgreSQL data. This API is then served by Apollo server and consumed by both their iOS and Android applications.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/helping-rapha-access-data-across-platforms-n3jfhtyu6rgn/index.mdx` at line 65, The sentence uses inconsistent pronouns ("help them develop its GraphQL API"); update the copy in the blog post to use a consistent plural pronoun by replacing "its" with "their" so the sentence reads "help them develop their GraphQL API" in the content of the MDX (look for the sentence starting "Rapha's mobile team uses Prisma...").apps/blog/content/blog/helping-rapha-access-data-across-platforms-n3jfhtyu6rgn/index.mdx-31-31 (1)
31-31:⚠️ Potential issue | 🟡 MinorFix spelling: use “wherever” (not “where ever”).
This is user-facing copy and should be corrected for publication quality.
✏️ Suggested copy fix
-Rapha's involvement with its community provides many unique opportunities and challenges. Offering products and services both online and in Rapha Clubhouses throughout the world helps them connect with users where ever they happen to be. These user touchpoints include Android and iOS applications, an e-commerce website, and a variety of web content like blog posts. +Rapha's involvement with its community provides many unique opportunities and challenges. Offering products and services both online and in Rapha Clubhouses throughout the world helps them connect with users wherever they happen to be. These user touchpoints include Android and iOS applications, an e-commerce website, and a variety of web content like blog posts.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/helping-rapha-access-data-across-platforms-n3jfhtyu6rgn/index.mdx` at line 31, In the sentence "Offering products and services both online and in Rapha Clubhouses throughout the world helps them connect with users where ever they happen to be." replace the incorrect two-word phrase "where ever" with the single word "wherever" so the user-facing copy reads correctly; update the string in the MDX content (the sentence containing "where ever they happen to be") accordingly.apps/blog/content/blog/e2e-type-safety-graphql-react-3-fbV2ZVIGWg/index.mdx-93-93 (1)
93-93:⚠️ Potential issue | 🟡 MinorTighten user-facing wording for clarity.
Small copy errors slipped into changed text:
- Line 93: “with the this snippet” → “with this snippet”
- Line 206: “resolvers, can now use” → “resolvers, you can now use”
- Line 257: “regenerate Prisma Client this each time” → “regenerate Prisma Client each time”
Also applies to: 206-206, 257-257
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/e2e-type-safety-graphql-react-3-fbV2ZVIGWg/index.mdx` at line 93, Fix three copy errors in the MDX content: change "with the this snippet" to "with this snippet" (occurs at the sentence referencing src/index.ts), change "resolvers, can now use" to "resolvers, you can now use" (the sentence mentioning resolvers), and change "regenerate Prisma Client this each time" to "regenerate Prisma Client each time" (the sentence about regenerating Prisma Client); locate and update those exact phrases in the article text so wording reads clearly.apps/blog/content/blog/e2e-type-safety-graphql-react-3-fbV2ZVIGWg/index.mdx-225-226 (1)
225-226:⚠️ Potential issue | 🟡 MinorFix malformed fenced code-block headers (
diffrendered as content).Line 225, Line 284, Line 310, Line 354, Line 413, Line 509, and Line 850 show
diffas a literal first line inside the code block. That should be the fence language (e.g.,```diff), not content, otherwise examples render oddly and copy/paste includes noise.Suggested patch pattern
-```prisma -diff +```diff // prisma/schema.prisma-```ts -diff +```diff // src/builder.tsAlso applies to: 284-285, 310-311, 354-355, 413-414, 509-510, 850-851
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/e2e-type-safety-graphql-react-3-fbV2ZVIGWg/index.mdx` around lines 225 - 226, Several fenced code blocks in the MDX (e2e-type-safety-graphql-react-3-fbV2ZVIGWg index.mdx) have the literal word "diff" as the first line inside the block instead of using it as the fence language; locate the affected code blocks (around the occurrences referenced: the blocks starting near lines 225, 284, 310, 354, 413, 509, 850) and change the opening fence to include the correct language token (e.g., ```prisma or ```ts) and remove the leading "diff" content line so the fence language is the first thing after the backticks; ensure each block's language matches the snippet type (prisma for schema.prisma examples, ts for TypeScript) and verify no extra "diff" lines remain inside the code blocks.apps/blog/content/blog/e2e-type-safety-graphql-react-4-JaHA8GbkER/index.mdx-454-454 (1)
454-454:⚠️ Potential issue | 🟡 MinorFix query object name typo for consistency
Line 454 says
GetUserDocument, but the article imports and usesGetUsersDocument(Lines 431, 445, 467). This inconsistency can mislead readers.Proposed fix
-This uses the `GetUserDocument` query object to request data from your API and return it in a properly typed variable. +This uses the `GetUsersDocument` query object to request data from your API and return it in a properly typed variable.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/e2e-type-safety-graphql-react-4-JaHA8GbkER/index.mdx` at line 454, The sentence currently references the wrong query object name; replace the singular GetUserDocument with the plural GetUsersDocument so it matches the imported/used query object (GetUsersDocument) in the article and avoids confusion for readers — update the text where the query object is described to use GetUsersDocument consistently with the imports and examples.apps/blog/content/blog/bfg/index.mdx-51-51 (1)
51-51:⚠️ Potential issue | 🟡 MinorFix the link label quoting/escaping to avoid odd Markdown rendering.
Line 51 currently mixes outer quotes, inner quotes, and escaped asterisks in a way that can render awkwardly (or inconsistently across MDX renderers). Make the linked phrase explicit and escape stars plainly.
Suggested fix
-Just like the "[Big F**\*\*** Gun"](<https://en.wikipedia.org/wiki/BFG_(weapon)>) from the massively popular games Doom & Quake, the 'Build, Fortify, Grow' framework (or BFG for short) provides a formidable toolkit for software development teams. With Prisma’s suite of products underpinning each phase, your development process isn't just equipped with a peashooter or a sidearm; it’s armed with the ultimate weapon when it comes to developing data-driven applications. +Just like the ["Big F\*\*\*\*\*\* Gun"](https://en.wikipedia.org/wiki/BFG_(weapon)) from the massively popular games Doom & Quake, the 'Build, Fortify, Grow' framework (or BFG for short) provides a formidable toolkit for software development teams. With Prisma’s suite of products underpinning each phase, your development process isn't just equipped with a peashooter or a sidearm; it’s armed with the ultimate weapon when it comes to developing data-driven applications.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/bfg/index.mdx` at line 51, The link label is currently mixing outer quotes and escaped asterisks causing odd MDX rendering; fix it by replacing the quoted/escaped label with a plain, explicit link label such as [Big F\*\*\* Gun](https://en.wikipedia.org/wiki/BFG_(weapon)) (no surrounding quotes), or alternatively use a backticked label or HTML entities for the asterisks; update the instance of "Big F**\*\*** Gun" in apps/blog/content/blog/bfg/index.mdx so the link text is a simple unquoted label with plainly escaped asterisks.apps/blog/content/blog/announcing-prisma-postgres-early-access/index.mdx-34-34 (1)
34-34:⚠️ Potential issue | 🟡 MinorFix broken in-page anchor link target.
Line 34 uses
##...inside the Markdown link destination, which won’t match the section anchor. Use a single#fragment.Suggested fix
-... Jump ahead to the [next section](##building-a-managed-postgresql-service-on-millisecond-cloud-infrastructure) ... +... Jump ahead to the [next section](`#building-a-managed-postgresql-service-on-millisecond-cloud-infrastructure`) ...🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/announcing-prisma-postgres-early-access/index.mdx` at line 34, The in-page anchor link uses a double-hash fragment ("##building-a-managed-postgresql-service-on-millisecond-cloud-infrastructure") which doesn't match the generated section ID; update the link target in the paragraph (the Markdown link URL that currently contains "##building-a-managed-postgresql-service-on-millisecond-cloud-infrastructure") to use a single hash "#building-a-managed-postgresql-service-on-millisecond-cloud-infrastructure" so the link correctly navigates to the "building-a-managed-postgresql-service-on-millisecond-cloud-infrastructure" heading.apps/blog/content/blog/announcing-prisma-2-n0v98rzc8br1/index.mdx-397-397 (1)
397-397:⚠️ Potential issue | 🟡 MinorFix grammar typo in user-facing content.
Line 397 says “Blitz is build on top of Next.js”; this should be “Blitz is built on top of Next.js.”
Suggested fix
-Another framework with increasing anticipation and excitement in the community is [Blitz.js](http://blitzjs.com/). Blitz is build on top of Next.js and takes a fundamentally different approach compared to Redwood. Its goal is to completely eliminate the API server and ["bring back the simplicity of server rendered frameworks"](https://github.com/blitz-js/blitz/blob/canary/rfc-docs/01-architecture.md#introduction). +Another framework with increasing anticipation and excitement in the community is [Blitz.js](http://blitzjs.com/). Blitz is built on top of Next.js and takes a fundamentally different approach compared to Redwood. Its goal is to completely eliminate the API server and ["bring back the simplicity of server rendered frameworks"](https://github.com/blitz-js/blitz/blob/canary/rfc-docs/01-architecture.md#introduction).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/announcing-prisma-2-n0v98rzc8br1/index.mdx` at line 397, Fix the grammar typo in the MDX content: replace the phrase "Blitz is build on top of Next.js" with "Blitz is built on top of Next.js" in the blog post content (the sentence containing "Blitz is build on top of Next.js" around line referencing that sentence in the MDX body). Ensure only the word "build" is changed to "built" and no other text is modified.apps/blog/content/blog/announcing-prisma-2-zq1s745db8i5/index.mdx-383-383 (1)
383-383:⚠️ Potential issue | 🟡 MinorRemove extra parentheses on line 373.
The code shows
const allUsers = await prisma.users()();but per the official Prisma 2 announcement post, the correct call shape for listing users isawait prisma.users()with only a single invocation. The extra()should be removed.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/announcing-prisma-2-zq1s745db8i5/index.mdx` at line 383, The line creating allUsers calls prisma.users with an extra invocation; change the usage so you await the single call to prisma.users() (i.e., replace the current await prisma.users()() pattern used when assigning to allUsers with awaiting prisma.users()). Update the assignment to use the single invocation form so the variable allUsers receives the result of await prisma.users().apps/blog/content/blog/convergence/index.mdx-135-135 (1)
135-135:⚠️ Potential issue | 🟡 MinorCorrect spelling error.
"mujst" should be "must".
📝 Proposed fix
-Here's the undeniable thing folks: we're not claiming they copied us (though we'd be flattered). We're claiming that when you build for production-scale relational queries, you mujst naturally converge on these patterns. They feel natural because they are fundamentally superior for developer experience and correctnes. +Here's the undeniable thing folks: we're not claiming they copied us (though we'd be flattered). We're claiming that when you build for production-scale relational queries, you must naturally converge on these patterns. They feel natural because they are fundamentally superior for developer experience and correctnes.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 135, Replace the misspelled word "mujst" with "must" in the sentence that reads "when you build for production-scale relational queries, you mujst naturally converge on these patterns" so the sentence correctly reads "when you build for production-scale relational queries, you must naturally converge on these patterns"; update the MDX content in the same paragraph where "must" currently appears misspelled.apps/blog/content/blog/convergence/index.mdx-137-137 (1)
137-137:⚠️ Potential issue | 🟡 MinorCorrect spelling error.
"stratight" should be "straight".
📝 Proposed fix
-The unavoidable takeaway comes stratight from Drizzle's [v2 migration documentation](https://rqbv2.drizzle-orm-fe.pages.dev/docs/relations-v1-v2), which lists the features conspicuously "not supported in v1": +The unavoidable takeaway comes straight from Drizzle's [v2 migration documentation](https://rqbv2.drizzle-orm-fe.pages.dev/docs/relations-v1-v2), which lists the features conspicuously "not supported in v1":🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 137, Fix the typo "stratight" to "straight" in the sentence that starts "The unavoidable takeaway comes stratight from Drizzle's [v2 migration documentation]..." (the line in the blog post content). Update that exact word so the sentence reads "The unavoidable takeaway comes straight from Drizzle's [v2 migration documentation]..." ensuring spacing and punctuation remain unchanged.apps/blog/content/blog/convergence/index.mdx-27-27 (1)
27-27:⚠️ Potential issue | 🟡 MinorCorrect spelling error.
"unavoidble" should be "unavoidable".
📝 Proposed fix
-The test suite expansion alone tells the unavoidble story. You don't go from 600 to over 9,000 tests because you're over-engineering. You do it because migrations are genuinely complex: handling edge cases across database vendors, tricky alterations (column renames, type changes), data preservation during schema evolution, and the intricacies of multi-dialect support safely. +The test suite expansion alone tells the unavoidable story. You don't go from 600 to over 9,000 tests because you're over-engineering. You do it because migrations are genuinely complex: handling edge cases across database vendors, tricky alterations (column renames, type changes), data preservation during schema evolution, and the intricacies of multi-dialect support safely.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 27, Replace the misspelled word "unavoidble" with the correct spelling "unavoidable" in the sentence that starts "The test suite expansion alone tells the unavoidble story." (update the string literal containing that sentence in the MDX content so it reads "The test suite expansion alone tells the unavoidable story.")apps/blog/content/blog/convergence/index.mdx-285-285 (1)
285-285:⚠️ Potential issue | 🟡 MinorCorrect spelling error.
"tthe" should be "the".
📝 Proposed fix
-These patterns aren't "Prisma patterns," they're solutions that emerge when solving production database problems. We got here first. We'd argue our path was more direct. But the observed convergence validates tthe destination. +These patterns aren't "Prisma patterns," they're solutions that emerge when solving production database problems. We got here first. We'd argue our path was more direct. But the observed convergence validates the destination.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 285, Fix the spelling typo by replacing the incorrect word "tthe" with "the" in the sentence that ends with "validates tthe destination." — locate the occurrence of "tthe" in the convergence content and update it to "the" so the sentence reads "...validates the destination."apps/blog/content/blog/convergence/index.mdx-19-19 (1)
19-19:⚠️ Potential issue | 🟡 MinorFix grammatical error in prose.
The phrase "to serve your the needs of your users" contains an extra word. Should be "to serve the needs of your users."
📝 Proposed fix
-Here's what makes this really cool: two ORMs with opposite starting philosophies, built by different teams, are converging on remarkably similar thinking and arch. This isn't about who copied whom, it's about discovering what production applications actually need, and then doing the necessary to serve your the needs of your users. It's also about what this convergence reveals: certain patterns aren't arbitrary preferences made by engineering teams or biased framework opinions, they're optimal solutions that emerge when you tackle production-scale problems in complicated domains like databases. +Here's what makes this really cool: two ORMs with opposite starting philosophies, built by different teams, are converging on remarkably similar thinking and arch. This isn't about who copied whom, it's about discovering what production applications actually need, and then doing the necessary to serve the needs of your users. It's also about what this convergence reveals: certain patterns aren't arbitrary preferences made by engineering teams or biased framework opinions, they're optimal solutions that emerge when you tackle production-scale problems in complicated domains like databases.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 19, In the sentence in apps/blog/content/blog/convergence/index.mdx that currently reads "to serve your the needs of your users", remove the stray word "your" so it reads "to serve the needs of your users."; update that exact phrase in the paragraph describing ORM convergence.apps/blog/content/blog/convergence/index.mdx-25-25 (1)
25-25:⚠️ Potential issue | 🟡 MinorCorrect spelling error.
"initialk" should be "initial".
📝 Proposed fix
-Let's talk about migrations. Drizzle has always offered schema-first migrations and automated tooling, and their initialk commands for the same have been remarkably similar to Prisma's from day one. But their ongoing Alternation Engine work now reveals something we learned the hard way back in 2021: building reliable migrations across databases isn't a weekend project, rather it's a sustained, core engineering effort. +Let's talk about migrations. Drizzle has always offered schema-first migrations and automated tooling, and their initial commands for the same have been remarkably similar to Prisma's from day one. But their ongoing Alternation Engine work now reveals something we learned the hard way back in 2021: building reliable migrations across databases isn't a weekend project, rather it's a sustained, core engineering effort.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/convergence/index.mdx` at line 25, Replace the misspelled token "initialk" in the MDX content sentence ("Let's talk about migrations... initialk commands...") with the correct word "initial" so the sentence reads "initial commands"; edit the string in the MDX document where "initialk" appears (e.g., in the paragraph containing "initialk commands for the same") to fix the typo.apps/blog/content/blog/fullstack-remix-prisma-mongodb-2-ZTmOy58p4re8/index.mdx-1186-1187 (1)
1186-1187:⚠️ Potential issue | 🟡 Minor
firstNameandlastNamedefaults are swapped in the example.These two assignments are reversed, so the snippet pre-fills the wrong fields after validation errors.
Suggested fix
- firstName: actionData?.fields?.lastName || "", - lastName: actionData?.fields?.firstName || "", + firstName: actionData?.fields?.firstName || "", + lastName: actionData?.fields?.lastName || "",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/fullstack-remix-prisma-mongodb-2-ZTmOy58p4re8/index.mdx` around lines 1186 - 1187, The default values for the form fields are swapped: change the assignments so firstName reads from actionData?.fields?.firstName (not lastName) and lastName reads from actionData?.fields?.lastName (not firstName); locate the object where firstName and lastName are set from actionData?.fields and swap the source fields so each property uses the matching field name.apps/blog/content/blog/fullstack-remix-prisma-mongodb-2-ZTmOy58p4re8/index.mdx-366-372 (1)
366-372:⚠️ Potential issue | 🟡 MinorUse a proper diff block (or clean TSX) for this snippet.
This block currently mixes
tsxcode with literal diff markers (diff,+), which makes the example hard to copy and easy to misread.Suggested cleanup
-```tsx -diff - // app/routes/login.tsx - <p className="font-semibold text-slate-300">Log In To Give Some Praise!</p> + - ( - <p className="font-semibold text-slate-300"> - + {action === "login" ? "Log In To Give Some Praise!" : "Sign Up To Get Started!"}+{" "} - </p> - ); +```diff +// app/routes/login.tsx +- <p className="font-semibold text-slate-300">Log In To Give Some Praise!</p> ++ <p className="font-semibold text-slate-300"> ++ {action === "login" ? "Log In To Give Some Praise!" : "Sign Up To Get Started!"} ++ </p></details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@apps/blog/content/blog/fullstack-remix-prisma-mongodb-2-ZTmOy58p4re8/index.mdx
around lines 366 - 372, The snippet contains literal diff markers ("diff", "+")
mixed into TSX making it invalid; remove the diff markers and replace with clean
JSX in the login component so the paragraph element renders the conditional
string based on the action variable (refer to action and theelement); ensure the JSX uses a single
that contains the ternary expression (action === "login" ? "Log In To Give Some Praise!" : "Sign Up To Get Started!") rather than duplicated lines with plus signs or diff headers, and wrap the final example in a proper TSX code block for the blog post. ```
apps/blog/content/blog/cloudflare-unikernels-and-bare-metal-life-of-a-prisma-postgres-query/index.mdx-112-112 (1)
112-112:⚠️ Potential issue | 🟡 MinorFix grammar in selection-field explanation.
Line 112 should read “will be returned from the database” (not “will be return”).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/cloudflare-unikernels-and-bare-metal-life-of-a-prisma-postgres-query/index.mdx` at line 112, Fix the grammar in the explanation of the selection argument: change the sentence that currently reads "which means that all scalar fields of the target model will be return from the database" to use the past participle "returned" so it reads "will be returned from the database"; update the text near the mention of the selection argument and the "$scalars": true example (references: selection, select, include, "$scalars": true) accordingly.apps/blog/content/blog/how-greatfrontend-supercharged-development-with-prisma-orm/index.mdx-19-20 (1)
19-20:⚠️ Potential issue | 🟡 MinorUse hyphenated compound adjective in role description.
On Line 19 and Line 20, use “front-end engineers” instead of “front end engineers” for grammatical consistency in the blog copy.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/how-greatfrontend-supercharged-development-with-prisma-orm/index.mdx` around lines 19 - 20, Update the role phrasing in the two list items that currently read "front end engineers" to the hyphenated compound adjective "front-end engineers"; locate and modify the phrase in the two entries that start "A [technical interview preparation platform]..." and "A [real-world projects platform]..." so both instances use "front-end engineers".apps/blog/content/blog/graphql-server-basics-the-network-layer-51d97d21861/index.mdx-218-218 (1)
218-218:⚠️ Potential issue | 🟡 MinorFix typo in returned greeting string.
Line 218 has an unintended double space (
"Hello World"), which makes the example output inconsistent with the rest of the article.Suggested fix
- hello: (root, args, context, info) => "Hello World", + hello: (root, args, context, info) => "Hello World",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/graphql-server-basics-the-network-layer-51d97d21861/index.mdx` at line 218, The example resolver for the hello field returns a string with an extra space; update the arrow function hello: (root, args, context, info) => "Hello World" to return "Hello World" (single space) so the greeting matches the rest of the examples and removes the double space.apps/blog/content/blog/advanced-database-schema-management-with-atlas-and-prisma-orm/index.mdx-47-47 (1)
47-47:⚠️ Potential issue | 🟡 MinorFix malformed Markdown link syntax in prerequisites paragraph.
Line 47 currently has invalid link markup (
[main examples](<](...)>)), so the link will not render correctly.Suggested fix
-For the purpose of this guide, we'll assume that your Prisma schema contains the standard `User` and `Post` models that we use as [main examples](<](https://www.prisma.io/docs/orm/overview/introduction/what-is-prisma#the-prisma-schema)>) across our documentation. +For the purpose of this guide, we'll assume that your Prisma schema contains the standard `User` and `Post` models that we use as [main examples](https://www.prisma.io/docs/orm/overview/introduction/what-is-prisma#the-prisma-schema) across our documentation.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/advanced-database-schema-management-with-atlas-and-prisma-orm/index.mdx` at line 47, The prerequisites paragraph contains a malformed Markdown link `[main examples](<](https://www.prisma.io/docs/orm/overview/introduction/what-is-prisma#the-prisma-schema)>)`; locate that string in the file (the sentence referencing Prisma `User` and `Post` models) and replace the broken markup with a valid Markdown link by removing the stray angle bracket and closing bracket so it reads like `[main examples](https://www.prisma.io/docs/orm/overview/introduction/what-is-prisma#the-prisma-schema)` ensuring the link renders correctly.apps/blog/content/blog/accelerate-static-ip-support/index.mdx-37-37 (1)
37-37:⚠️ Potential issue | 🟡 MinorCorrect subject-verb agreement in the static IP definition sentence.
Line 37 should use singular agreement: “traffic … is easier to identify.”
Suggested fix
-A static IP address is an IPv4 or an IPv6 address that doesn’t change. Unlike dynamic IP addresses, which can change unpredictably, traffic from static IP addresses are easier to identify. +A static IP address is an IPv4 or an IPv6 address that doesn’t change. Unlike dynamic IP addresses, which can change unpredictably, traffic from static IP addresses is easier to identify.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/accelerate-static-ip-support/index.mdx` at line 37, The sentence beginning "A static IP address is an IPv4 or an IPv6 address that doesn’t change..." has incorrect subject-verb agreement in the clause "traffic from static IP addresses are easier to identify"; change "are" to "is" so the clause reads "traffic from static IP addresses is easier to identify." Ensure only that verb is updated and punctuation/spacing remain unchanged.apps/blog/content/blog/connections-edges-nodes-in-relay-758d358aa4c7/index.mdx-14-14 (1)
14-14:⚠️ Potential issue | 🟡 MinorFix duplicated period in explanatory paragraph.
Line 14 currently ends with
models..; this should be a single period.✍️ Suggested edit
-of GraphQL, mainly in order to manage relationships between models.. +of GraphQL, mainly in order to manage relationships between models.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/connections-edges-nodes-in-relay-758d358aa4c7/index.mdx` at line 14, Replace the duplicated period at the end of the explanatory sentence that currently reads "of GraphQL, mainly in order to manage relationships between models.." by changing "models.." to "models." so the sentence ends with a single period; update the MDX content where that exact phrase appears.apps/blog/content/blog/announcing-prisma-day-50cg22nn40qk/index.mdx-14-14 (1)
14-14:⚠️ Potential issue | 🟡 MinorRemove duplicated punctuation in intro sentence.
Line 14 ends with
models.., which should be a single period in published copy.✍️ Suggested edit
-of GraphQL, mainly in order to manage relationships between models.. +of GraphQL, mainly in order to manage relationships between models.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/announcing-prisma-day-50cg22nn40qk/index.mdx` at line 14, The intro sentence contains a duplicated period ("models..")—open the MDX file (apps/blog/content/blog/announcing-prisma-day-50cg22nn40qk/index.mdx), locate the intro line that reads "intersection of modern app development, databases, and Prisma in production." or specifically the fragment ending with "models..", and replace the double period with a single period so it reads "models."; ensure no other punctuation duplication remains in the surrounding sentence.apps/blog/content/blog/compliance-reqs-complete/index.mdx-49-49 (1)
49-49:⚠️ Potential issue | 🟡 MinorFix grammar in customer-facing copy.
Line 49 should read “this is not a one-time effort” to avoid a published text error.
✍️ Suggested edit
-Those who understand the compliance process and have gone through it know that this not a one-time effort but a continuous process of improvement. +Those who understand the compliance process and have gone through it know that this is not a one-time effort but a continuous process of improvement.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/compliance-reqs-complete/index.mdx` at line 49, The sentence currently reads "this not a one-time effort" and should be corrected to "this is not a one-time effort"; update the copy in the paragraph that mentions completing and maintaining SOC2 Type II, HIPAA, GDPR, and ISO 27001:2022 certifications (the sentence beginning "Those who understand the compliance process...") to insert the missing "is" so the customer-facing text reads correctly.apps/blog/content/blog/announcing-prisma-6-18-0/index.mdx-21-21 (1)
21-21:⚠️ Potential issue | 🟡 MinorFix pronoun inconsistency in the metrics sentence.
Line [21] mixes perspectives (
their+your), which reads awkwardly in user-facing copy.Suggested wording
-Last release, we included a new workspace metrics overview, so folks can get a quick glance on their usage data across your entire workspace. Now, we’ve added more insights into your database usage with database metrics. +Last release, we included a new workspace metrics overview, so folks can get a quick glance at usage data across their entire workspace. Now, we’ve added more insights into database usage with database metrics.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/announcing-prisma-6-18-0/index.mdx` at line 21, The sentence "Last release, we included a new workspace metrics overview, so folks can get a quick glance on their usage data across your entire workspace. Now, we’ve added more insights into your database usage with database metrics." mixes perspectives ("their" vs "your"); edit this copy to use a single consistent pronoun (either both "your" or both "their") so the sentence reads consistently—e.g., change "their usage data across your entire workspace" to "your usage data across your entire workspace" (or to "their usage data across their entire workspace") within the blog post content so the pronouns match.
🧹 Nitpick comments (6)
apps/blog/content/blog/graphql-directive-permissions-authorization-made-easy-54c076b5368e/index.mdx (1)
14-14: Tighten phrasing for readability at Line 14.Consider replacing “in order to” with “to” for more concise prose.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/graphql-directive-permissions-authorization-made-easy-54c076b5368e/index.mdx` at line 14, Replace the phrase "in order to" with "to" in the sentence containing "our guest author [Dennis Walsh](https://twitter.com/lawjolla) explains how to use them in order to protect your data." so it reads "...explains how to use them to protect your data." — update that exact sentence in the MDX content.apps/blog/content/blog/graphql-vs-firebase-496498546142/index.mdx (1)
14-14: Optional: strengthen phrasing in the intro sentence.At Line 14, “we want to explore” reads a bit tentative; consider a stronger form like “we explore” for a more confident opening.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/graphql-vs-firebase-496498546142/index.mdx` at line 14, Replace the tentative phrasing "we want to explore" with a stronger, declarative form — for example change the sentence containing "we want to explore the differences between Firebase and" to "we explore the differences between Firebase and" (update the sentence in the intro paragraph where the phrase appears).apps/blog/content/blog/backend-prisma-typescript-orm-with-postgresql-rest-api-validation-dcba1ps7kip3/index.mdx (1)
542-542: Use a proper diff snippet format for this replacement example.The current one-line
diff - (...) + (...)pattern is hard to follow in atsblock. Prefer a standard diff block (or plain before/after lines) so readers can copy changes confidently.Suggested doc snippet rewrite
-```ts -diff - (await server.register([status, prisma])) + (await server.register([status, prisma, users])); -``` +```diff +- await server.register([status, prisma]); ++ await server.register([status, prisma, users]); +```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/backend-prisma-typescript-orm-with-postgresql-rest-api-validation-dcba1ps7kip3/index.mdx` at line 542, The current inline diff "(await server.register([status, prisma])) + (await server.register([status, prisma, users]))" is hard to read; replace it with a standard diff/code block showing before and after (e.g., a fenced ts block or a unified diff) that clearly presents the original call to server.register([status, prisma]) and the updated call to server.register([status, prisma, users]) so readers can copy the change; update the snippet around the symbol server.register to use explicit "-" and "+" lines or separate "Before:" / "After:" lines inside a fenced ts block.apps/blog/content/blog/backend-prisma-typescript-orm-with-postgresql-auth-mngp1ps7kip4/index.mdx (1)
644-659: Typo in exported auth strategy constant name should be corrected.
API_AUTH_STATEGYappears to be a misspelling ofAPI_AUTH_STRATEGY. Even if internally consistent, this is tutorial-facing API naming that readers will propagate.💡 Suggested refactor
-export const API_AUTH_STATEGY = "API"; +export const API_AUTH_STRATEGY = "API"; -server.auth.strategy(API_AUTH_STATEGY, "jwt", { +server.auth.strategy(API_AUTH_STRATEGY, "jwt", { -server.auth.default(API_AUTH_STATEGY); +server.auth.default(API_AUTH_STRATEGY);🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/backend-prisma-typescript-orm-with-postgresql-auth-mngp1ps7kip4/index.mdx` around lines 644 - 659, Rename the misspelled exported constant API_AUTH_STATEGY to API_AUTH_STRATEGY and update all usages to match (e.g., the export line and references inside authPlugin.register where server.auth.strategy(API_AUTH_STATEGY, ...) and server.auth.default(API_AUTH_STATEGY) are called); ensure any imports or references elsewhere in the codebase (tests, docs, other modules) are updated to the new name to avoid runtime/import errors and keep the tutorial-facing API consistent.apps/blog/content/blog/e2e-type-safety-graphql-react-3-fbV2ZVIGWg/index.mdx (1)
504-504: Consider concise phrasing in two instructional sentences.Nice-to-have polish:
- Line 504: “you have the ability to” → “you can”
- Line 546: “In order to better visualize” → “To better visualize”
Also applies to: 546-546
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/e2e-type-safety-graphql-react-3-fbV2ZVIGWg/index.mdx` at line 504, Edit the two sentences for concise phrasing: inside the paragraph referencing the queryType function (line mentioning queryType) replace “you have the ability to” with “you can”; and in the later sentence that starts “In order to better visualize” (the line around the visualization example) change it to “To better visualize.” Make only these wording changes to the sentences to keep the meaning but tighten the phrasing.apps/blog/content/blog/fullstack-remix-prisma-mongodb-4-l3mwep4zlim2/index.mdx (1)
801-804: Prefer functionalsetFormDataafter async upload.Using the captured
formDataobject here can drop concurrent user edits. A functional update is safer.Suggested fix
- setFormData({ - ...formData, - profilePicture: imageUrl - }) + setFormData((prev) => ({ + ...prev, + profilePicture: imageUrl, + }))🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/fullstack-remix-prisma-mongodb-4-l3mwep4zlim2/index.mdx` around lines 801 - 804, After the async upload, avoid using the captured formData object and switch to a functional state update for setFormData to prevent lost concurrent edits: call setFormData(prev => ({ ...prev, profilePicture: imageUrl })) instead of referencing formData directly so updates merge safely; update the code that currently does setFormData({ ...formData, profilePicture: imageUrl }) to use this functional form (referencing setFormData, formData, profilePicture, imageUrl).
| - [Stale-While-Revalidate](https://www.prisma.io/docs/accelerate/caching#stale-while-revalidate-swr) (`swr`): Allows Prisma Postgres to serve _stale_ cached data while fetching fresh data in the background. When you set an SWR value, Prisma Postgres will continue to serve the cached data for that duration, even if it's past the TTL, while simultaneously updating the cache with new data from the database. | ||
|
|
||
| In this example, the data will be considered fresh for 30 seconds (TTL). After that, for the next 60 seconds (SWR), Prisma Postgres's cache will serve the stale data while fetching fresh data in the background. | ||
| In this example, the data will be considered fresh for 30 seconds (TTL). After that, for the next 60 seconds (SWR), Prisma Postgres's cache will serve the stale data while fetching fresh data in the background. |
Contributor
There was a problem hiding this comment.
Fix TTL/SWR durations to match the code example.
Line 87 inverts the values from the snippet above (ttl: 60, swr: 30). This makes the explanation technically incorrect.
Suggested wording fix
-In this example, the data will be considered fresh for 30 seconds (TTL). After that, for the next 60 seconds (SWR), Prisma Postgres's cache will serve the stale data while fetching fresh data in the background.
+In this example, the data will be considered fresh for 60 seconds (TTL). After that, for the next 30 seconds (SWR), Prisma Postgres's cache will serve stale data while fetching fresh data in the background.📝 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.
Suggested change
| In this example, the data will be considered fresh for 30 seconds (TTL). After that, for the next 60 seconds (SWR), Prisma Postgres's cache will serve the stale data while fetching fresh data in the background. | |
| In this example, the data will be considered fresh for 60 seconds (TTL). After that, for the next 30 seconds (SWR), Prisma Postgres's cache will serve stale data while fetching fresh data in the background. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@apps/blog/content/blog/cloudflare-unikernels-and-bare-metal-life-of-a-prisma-postgres-query/index.mdx`
at line 87, The sentence describing TTL/SWR durations is inverted compared to
the code example (the snippet uses ttl: 60 and swr: 30); update the prose so it
matches the example by stating that data is fresh for 60 seconds (TTL) and then
served stale for 30 seconds (SWR) while fresh data is fetched in the background,
referencing the ttl and swr values shown in the snippet.
oxfmt 0.46 corrupts MDX with embedded JSX and rewrites YAML frontmatter quote style. Skip .mdx entirely so `pnpm check` stays idempotent and blog MDX compiles.
AmanVarshney01
force-pushed
the
chore/update-oxlint-oxfmt
branch
from
16647e1 to
4c322de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
oxfmt^0.33.0→^0.46.0andoxlint^1.48.0→^1.61.0inpnpm-workspace.yaml.**/public/**toignorePatternsin both.oxfmtrc.jsonand.oxlintrc.jsonso vendor/static assets underpublic/are no longer touched.pnpm checkproduced across the repo with the new oxfmt version (mostly'→"and similar style-level changes).Summary by CodeRabbit