feat/update-default-published-state #2009
Conversation
✅ Deploy Preview for hyprnote-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for hyprnote ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThe PR changes the articles collection schema to default the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes All changes are homogeneous repetitions of the same pattern (adding a single metadata field), with no logic modifications, control-flow changes, or functional complexity. Possibly related PRs
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (41)
apps/web/content-collections.ts(1 hunks)apps/web/content/articles/ai-meeting-summary-tools.mdx(1 hunks)apps/web/content/articles/best-ai-meeting-assistant-for-taking-notes.mdx(1 hunks)apps/web/content/articles/best-ai-notetaker-for-in-person-meetings.mdx(1 hunks)apps/web/content/articles/best-ai-notetaker-for-microsoft-teams.mdx(1 hunks)apps/web/content/articles/best-ai-notetaker-for-zoom.mdx(1 hunks)apps/web/content/articles/best-ai-notetakers-google-meet.mdx(1 hunks)apps/web/content/articles/bot-free-ai-meeting-assistants.mdx(1 hunks)apps/web/content/articles/can-you-transcribe-meetings-without-sending-data-to-cloud.mdx(1 hunks)apps/web/content/articles/chatgpt-for-meeting-notes.mdx(1 hunks)apps/web/content/articles/choosing-a-cms.mdx(1 hunks)apps/web/content/articles/enterprise-ai-notetaking-tools.mdx(1 hunks)apps/web/content/articles/fathom-ai-alternatives.mdx(1 hunks)apps/web/content/articles/fireflies-ai-alternatives.mdx(1 hunks)apps/web/content/articles/free-ai-notetakers.mdx(1 hunks)apps/web/content/articles/free-transcription-software.mdx(1 hunks)apps/web/content/articles/google-gemini-meeting-notes.mdx(1 hunks)apps/web/content/articles/granola-ai-alternatives.mdx(1 hunks)apps/web/content/articles/how-to-have-productive-one-on-one-meetings.mdx(1 hunks)apps/web/content/articles/how-to-participate-in-meetings-effectively.mdx(1 hunks)apps/web/content/articles/how-to-reduce-meeting-fatigue.mdx(1 hunks)apps/web/content/articles/how-to-transcribe-zoom-calls.mdx(1 hunks)apps/web/content/articles/is-ai-notetaking-legal.mdx(1 hunks)apps/web/content/articles/is-fireflies-ai-safe.mdx(1 hunks)apps/web/content/articles/is-otter-ai-safe.mdx(1 hunks)apps/web/content/articles/local-ai-privacy-tools.mdx(1 hunks)apps/web/content/articles/meeting-minutes-software.mdx(1 hunks)apps/web/content/articles/meeting-preparation-checklist.mdx(1 hunks)apps/web/content/articles/open-source-meeting-transcription-software.mdx(1 hunks)apps/web/content/articles/otter-ai-alternatives.mdx(1 hunks)apps/web/content/articles/otter-ai-review.mdx(1 hunks)apps/web/content/articles/plaud-ai-alternatives.mdx(1 hunks)apps/web/content/articles/post-yc-slump.mdx(1 hunks)apps/web/content/articles/sales-ai-note-takers.mdx(1 hunks)apps/web/content/articles/see-zoom-meeting-history.mdx(1 hunks)apps/web/content/articles/tldv-review.mdx(1 hunks)apps/web/content/articles/using-ide-for-writing.mdx(1 hunks)apps/web/content/articles/what-makes-reliable-ai-note-taker.mdx(1 hunks)apps/web/content/articles/why-our-cms-is-github.mdx(1 hunks)apps/web/content/articles/why-we-burned-it-down.mdx(1 hunks)apps/web/content/articles/zoom-ai-companion-review.mdx(1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.ts
📄 CodeRabbit inference engine (CLAUDE.md)
**/*.ts: Agent implementations should use TypeScript and follow the established architectural patterns defined in the agent framework
Agent communication should use defined message protocols and interfaces
Files:
apps/web/content-collections.ts
**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
**/*.{ts,tsx}: Avoid creating a bunch of types/interfaces if they are not shared. Especially for function props, just inline them instead.
Never do manual state management for form/mutation. Use useForm (from tanstack-form) and useQuery/useMutation (from tanstack-query) instead for 99% of cases. Avoid patterns like setError.
If there are many classNames with conditional logic, usecn(import from@hypr/utils). It is similar toclsx. Always pass an array and split by logical grouping.
Usemotion/reactinstead offramer-motion.
Files:
apps/web/content-collections.ts
🪛 LanguageTool
apps/web/content/articles/choosing-a-cms.mdx
[style] ~52-~52: ‘almost never’ might be wordy. Consider a shorter alternative.
Context: ...n does content structure change?** - almost never (simple posts, titles, tags) - som...
(EN_WORDINESS_PREMIUM_ALMOST_NEVER)
[style] ~112-~112: Consider using a synonym to be more concise.
Context: ...ace include TinaCMS, Decap, etc., which a lot of devs compare as “Git-based CMS for Reac...
(A_LOT_OF)
[style] ~149-~149: Consider using a synonym to be more concise.
Context: ...great when you have multiple frontends, lots of content types, and non-technical editor...
(A_LOT_OF)
[style] ~186-~186: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...om/docs?utm_source=chatgpt.com) It’s very good if you want: - a hosted, beautiful doc...
(EN_WEAK_ADJECTIVE)
[style] ~186-~186: This phrasing can be overused. Try elevating your writing with a more formal alternative.
Context: ...m_source=chatgpt.com) It’s very good if you want: - a hosted, beautiful docs site - s...
(IF_YOU_WANT)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
- GitHub Check: Redirect rules - hyprnote
- GitHub Check: Header rules - hyprnote
- GitHub Check: Pages changed - hyprnote
- GitHub Check: ci (macos, macos-14)
- GitHub Check: fmt
🔇 Additional comments (42)
apps/web/content/articles/best-ai-notetaker-for-microsoft-teams.mdx (1)
6-6: Metadata change looks good.The addition of
published: truealigns with the schema default change to maintain this article's published state.apps/web/content/articles/best-ai-meeting-assistant-for-taking-notes.mdx (1)
6-6: Metadata update consistent with schema change.Article remains published with explicit flag.
apps/web/content/articles/granola-ai-alternatives.mdx (1)
6-6: Metadata flag correctly added.Article marked as published as intended.
apps/web/content/articles/open-source-meeting-transcription-software.mdx (1)
7-7: Metadata update correctly applied.Article marked as published.
apps/web/content/articles/plaud-ai-alternatives.mdx (1)
7-7: Metadata change correct.Article marked as published as intended.
apps/web/content/articles/what-makes-reliable-ai-note-taker.mdx (1)
7-7: Metadata update consistent.Article remains published with explicit flag.
apps/web/content/articles/fathom-ai-alternatives.mdx (1)
6-6: Metadata flag added correctly.Article marked as published.
apps/web/content/articles/why-we-burned-it-down.mdx (1)
7-7: Metadata flag correctly added.Article marked as published alongside existing
featured: trueflag.apps/web/content/articles/meeting-minutes-software.mdx (1)
1-8: Published field added correctly.The
published: trueflag has been properly inserted into the front matter at the correct position, maintaining YAML structure integrity.apps/web/content/articles/see-zoom-meeting-history.mdx (1)
1-9: Published field added correctly.The
published: trueflag is properly positioned in the front matter betweencreatedandcoverImagefields.apps/web/content/articles/post-yc-slump.mdx (1)
1-9: Published field added correctly.Metadata addition is syntactically correct and consistently placed within the front matter.
apps/web/content/articles/sales-ai-note-takers.mdx (1)
1-9: Published field added correctly.The front matter modification follows the established pattern and maintains proper YAML structure.
apps/web/content/articles/how-to-transcribe-zoom-calls.mdx (1)
1-8: Published field added correctly.Metadata change is properly integrated into the front matter.
apps/web/content/articles/enterprise-ai-notetaking-tools.mdx (1)
1-9: Published field added correctly.Front matter modification is syntactically sound and positioned consistently.
apps/web/content/articles/otter-ai-review.mdx (1)
1-8: Published field added correctly.YAML front matter change is properly structured.
apps/web/content/articles/how-to-have-productive-one-on-one-meetings.mdx (1)
1-9: Published field added correctly.Metadata addition maintains proper YAML formatting and is consistently positioned.
apps/web/content/articles/fireflies-ai-alternatives.mdx (1)
6-6: Metadata update approved: article publication state.The added
published: truefront matter field correctly marks this article as published. This aligns with the PR's schema migration where the collection default changed to unpublished state, requiring explicit publication flags on existing articles.apps/web/content/articles/free-transcription-software.mdx (1)
7-7: Metadata update approved: article publication state.The
published: truefield has been added to mark this article as published, consistent with the PR's schema migration.apps/web/content/articles/how-to-reduce-meeting-fatigue.mdx (1)
6-6: Metadata update approved: article publication state.The
published: truefield marks this article as published as part of the schema migration.apps/web/content/articles/otter-ai-alternatives.mdx (1)
6-6: Metadata update approved: article publication state.The
published: truefield marks this article as published as part of the collection schema migration.apps/web/content/articles/best-ai-notetaker-for-zoom.mdx (1)
6-6: Metadata update approved: article publication state.The
published: truefield marks this article as published consistent with the schema migration.apps/web/content/articles/best-ai-notetakers-google-meet.mdx (1)
6-6: Metadata update approved: article publication state.The
published: truefield marks this article as published as part of the collection schema migration.apps/web/content/articles/using-ide-for-writing.mdx (1)
7-7: Metadata update approved: article publication state.The
published: truefield marks this article as published as part of the schema migration.apps/web/content/articles/is-ai-notetaking-legal.mdx (2)
6-6: Metadata update approved: article publication state.The
published: truefield marks this article as published as part of the schema migration.
1-8: Verify: PR summary mentions 39 files changed, but only 8 provided for review.The AI summary states the PR changes 39 existing article files by adding
published: true, but only 8 article files were provided in this review. Please confirm:
- Are all 39 files included in this PR, or is the summary inaccurate?
- If additional files exist beyond these 8, ensure they all follow the same pattern for consistency.
apps/web/content/articles/zoom-ai-companion-review.mdx (1)
6-6: Front matter metadata update aligns with PR objective.The addition of
published: truecorrectly marks this article as published, consistent with the PR's migration to an explicit publication flag pattern.apps/web/content/articles/can-you-transcribe-meetings-without-sending-data-to-cloud.mdx (1)
6-6: Front matter metadata update is correct.Addition of
published: trueproperly marks this article for publication under the new schema default.apps/web/content/articles/google-gemini-meeting-notes.mdx (1)
6-6: Front matter metadata update is correct.Addition of
published: trueproperly marks this article for publication.apps/web/content/articles/choosing-a-cms.mdx (1)
8-8: Front matter metadata is correct (pending content cleanup).The
published: trueaddition is appropriate, but merge should be blocked until the citation artifacts are removed from the file body.apps/web/content/articles/why-our-cms-is-github.mdx (1)
6-6: Front matter metadata update is correct.Addition of
published: trueproperly marks this article for publication.apps/web/content/articles/bot-free-ai-meeting-assistants.mdx (1)
6-6: Front matter metadata is correct (pending URL fixes).The
published: trueaddition is appropriate, but merge should be blocked until the malformed URLs below are corrected.apps/web/content/articles/free-ai-notetakers.mdx (1)
6-6: Front matter metadata update is correct.Addition of
published: trueproperly marks this article for publication.apps/web/content/articles/how-to-participate-in-meetings-effectively.mdx (1)
7-7: Front matter metadata update is correct.Addition of
published: trueproperly marks this article for publication. Field placement is appropriate within the front matter structure.apps/web/content/articles/is-fireflies-ai-safe.mdx (1)
6-6: Syntactically correct front matter addition.Line 6 correctly adds
published: trueto the YAML front matter in valid syntax. The placement betweencreatedandcoverImagefields follows conventional ordering.However, verification is needed to ensure:
- The schema change in
apps/web/content-collections.tsactually changed the default fromtruetofalse- All 39 articles mentioned in the PR summary were updated (only 8 files provided for review)
- No articles were missed in the update batch
Run the verification script provided to check schema changes and article completeness across the full repository.
apps/web/content/articles/chatgpt-for-meeting-notes.mdx (1)
6-6: Pattern verified: consistent with file 1.The
published: trueaddition matches the pattern from the previous article file. No issues with syntax or placement.apps/web/content/articles/tldv-review.mdx (1)
7-7: Pattern continues:published: trueaddition is syntactically correct.Third article following the same pattern. All syntax and placement are correct.
apps/web/content/articles/is-otter-ai-safe.mdx (1)
6-6: Syntax correct: Pattern consistency maintained.Fourth article with identical pattern and valid YAML syntax.
apps/web/content/articles/local-ai-privacy-tools.mdx (1)
6-6: Consistent pattern: Syntactically valid.Fifth article following established pattern.
apps/web/content/articles/meeting-preparation-checklist.mdx (1)
7-7: Pattern maintained: Valid YAML addition.Sixth article with expected pattern.
apps/web/content/articles/ai-meeting-summary-tools.mdx (1)
8-8: Consistent pattern: Placement and syntax verified.Seventh article following the established pattern. Placement after
createdand beforecoverImageis consistent with other files.apps/web/content/articles/best-ai-notetaker-for-in-person-meetings.mdx (1)
6-6: Pattern verification complete: All 8 files syntactically correct.All provided articles correctly add
published: truein valid YAML syntax with consistent placement and formatting.apps/web/content-collections.ts (1)
49-49: Schema change is safe—migration and filtering verified.All 42 articles have explicit
publishedfields, with 41 marked astrueand 1 intentionallyfalse. The filter logic across the codebase (published !== false) correctly handles the new default, showing published articles in production while displaying all articles in development mode for testing. No content will be inadvertently hidden.
| author: "John Jeong" | ||
| created: "2025-08-27" | ||
| published: true | ||
| coverImage: "https://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_imageshttps://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/blog/bot-free-ai-meeting-assistants/cover.png" |
There was a problem hiding this comment.
Fix malformed coverImage and image URLs.
Lines 7 and 52 contain URLs that concatenate improperly, resulting in invalid paths. The string public_images merges directly with the https:// protocol without proper separation.
Line 7 (coverImage):
Current: public_imageshttps://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/...
Expected: public_images/blog/bot-free-ai-meeting-assistants/cover.png
Line 52 (img src):
Same issue — URL segment duplicated without separator.
Apply this diff to fix line 7:
-coverImage: "https://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_imageshttps://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/blog/bot-free-ai-meeting-assistants/cover.png"
+coverImage: "https://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/blog/bot-free-ai-meeting-assistants/cover.png"Apply this diff to fix line 52:
-<img src="https://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_imageshttps://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/blog/bot-free-ai-meeting-assistants/hyprnote.webp" alt="Hyprnote"/>
+<img src="https://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/blog/bot-free-ai-meeting-assistants/hyprnote.webp" alt="Hyprnote"/>Also applies to: 52-52
🤖 Prompt for AI Agents
In apps/web/content/articles/bot-free-ai-meeting-assistants.mdx around lines 7
and 52, the coverImage and img src URLs are malformed because the segment
"public_images" is concatenated directly with the full https:// host, producing
"public_imageshttps://..."; replace both occurrences with the correct full URL
that includes the missing path separator and blog folder, e.g.
"https://ijoptyyjrfqwaqhyxkxj.supabase.co/storage/v1/object/public/public_images/blog/bot-free-ai-meeting-assistants/cover.png"
for line 7 and the corresponding image filename path under the same
"/public_images/blog/bot-free-ai-meeting-assistants/" directory for line 52 so
the URLs are valid and not duplicated.
| Pros: | ||
|
|
||
| - maximum **portability** (plain files last decades) | ||
| - works perfectly with modern frameworks (Next.js, TanStack Start, Astro) via MDX support [oai_citation:0‡Next.js](https://nextjs.org/docs/pages/guides/mdx?utm_source=chatgpt.com) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, check if file exists and its size
wc -l apps/web/content/articles/choosing-a-cms.mdxRepository: fastrepl/hyprnote
Length of output: 109
🏁 Script executed:
# Find all oai_citation markers with line numbers
rg -n 'oai_citation' apps/web/content/articles/choosing-a-cms.mdxRepository: fastrepl/hyprnote
Length of output: 3684
Remove web search citation artifacts before publishing.
This file contains 18 oai_citation markers embedded throughout the content. These are unintended artifacts from web search or citation generation that will render as literal text in published content, breaking the user experience.
Found at lines: 91, 110, 112, 139, 145, 146, 153, 156, 157, 164, 184, 190, 199, 215, 294, 296, 298.
Examples:
[oai_citation:0‡Next.js](https://nextjs.org/docs/pages/guides/mdx?utm_source=chatgpt.com)
[oai_citation:1‡Keystatic](https://keystatic.com/?utm_source=chatgpt.com)
Remove all [oai_citation:*‡*] patterns before merging.
🤖 Prompt for AI Agents
In apps/web/content/articles/choosing-a-cms.mdx around lines 91-298, there are
unwanted web-search citation artifacts of the form [oai_citation:*‡*] present at
the listed lines; remove all occurrences of the pattern (e.g.
[oai_citation:0‡Next.js]) so they do not appear in published content by
searching the file for the regex \[oai_citation:[^\]]+\] and deleting each match
(or manually remove the 18 specific markers at lines 91, 110, 112, 139, 145,
146, 153, 156, 157, 164, 184, 190, 199, 215, 294, 296, 298), then save and
verify the rendered MDX no longer contains any oai_citation tokens.
No description provided.