Repository navigation
docs: What's new in 0.28.0 - #394
Conversation
Signed-off-by: Ilya Boyandin <[email protected]>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (16)
📝 WalkthroughWalkthroughReorganizes the Tailwind v3→v4 upgrade instructions into a step-based manual flow, adds a 0.28.0 release section documenting Tailwind v4, Cosmos.gl, and a Command system, and updates the multi-room example README with a demo link and expanded feature descriptions. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 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
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
examples/multi-room/README.md (1)
25-28:⚠️ Potential issue | 🟠 MajorAdd
pnpm buildbeforepnpm devin local run stepsExamples linked via
workspace:*can fail if packages are not built first. Addpnpm buildto the documented sequence. Based on learnings: Runpnpm buildbefore running any example app, as examples depend on builtsqlrooms/*packages viaworkspace:*links.Suggested doc patch
```sh pnpm install +pnpm build pnpm dev</details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@examples/multi-room/README.mdaround lines 25 - 28, Update the example
startup sequence code block that currently lists "pnpm install" followed by
"pnpm dev" to insert "pnpm build" between them; locate the fenced shell snippet
containing the lines "pnpm install" and "pnpm dev" and add a new line "pnpm
build" so examples using workspace:* packages are built before running.</details> </blockquote></details> </blockquote></details>🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed. Inline comments: In `@docs/upgrade-guide.md`: - Around line 22-43: The numbered list in the migration instructions is inconsistent (multiple "1" entries then "2" etc.); update the sequence in docs/upgrade-guide.md so the steps are strictly increasing (e.g., 1, 2, 3, 4, 5) and ensure the items referencing index.css, tailwind.config.js, and removing `@layer base { ... }` are renumbered correctly to reflect their order, keeping the same text content but fixing the numeric prefixes. In `@examples/multi-room/README.md`: - Line 4: Update the README reference text: replace the string "Github repo" with the correctly cased "GitHub repo" in the examples/multi-room README (look for the table entry containing the link text "[Github repo](https://github.com/sqlrooms/sqlrooms/tree/main/examples/multi-room)"). --- Outside diff comments: In `@examples/multi-room/README.md`: - Around line 25-28: Update the example startup sequence code block that currently lists "pnpm install" followed by "pnpm dev" to insert "pnpm build" between them; locate the fenced shell snippet containing the lines "pnpm install" and "pnpm dev" and add a new line "pnpm build" so examples using workspace:* packages are built before running.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
docs/media/whats-new/commands.mp4is excluded by!**/*.mp4📒 Files selected for processing (3)
docs/upgrade-guide.mddocs/whats-new.mdexamples/multi-room/README.md
Signed-off-by: Ilya Boyandin <[email protected]>
…-new-in-0.28.0 Signed-off-by: Ilya Boyandin <[email protected]>
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/upgrade-guide.md (1)
88-112:⚠️ Potential issue | 🟡 MinorFix duplicate Step 4 numbering.
Both the Vite instructions (line 88) and NextJS instructions (line 112) are labeled as "Step 4". The NextJS section should be labeled "Step 5" to maintain sequential numbering throughout the migration checklist.
📝 Proposed fix
-##### Step 4: For NextJS projects +##### Step 5: For NextJS projects🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/upgrade-guide.md` around lines 88 - 112, The document has duplicated "Step 4" headings: "Step 4: For Vite projects" and "Step 4: For NextJS projects"; update the NextJS section heading to "Step 5: For NextJS projects" to restore proper sequential numbering (locate the heading text "Step 4: For NextJS projects" in the diff and change the numeral to 5).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@docs/upgrade-guide.md`:
- Around line 88-112: The document has duplicated "Step 4" headings: "Step 4:
For Vite projects" and "Step 4: For NextJS projects"; update the NextJS section
heading to "Step 5: For NextJS projects" to restore proper sequential numbering
(locate the heading text "Step 4: For NextJS projects" in the diff and change
the numeral to 5).
Signed-off-by: Ilya Boyandin <[email protected]>
Summary by CodeRabbit
New Features
Documentation
Examples