Skip to content

Conversation

@bartholomej
Copy link
Owner

@bartholomej bartholomej commented Dec 2, 2025

Description

  • Better DX and styling in readme

Type of change

  • Bug fix
  • New feature
  • Refactoring (no functional changes)
  • Code style update
  • Build / CI related changes
  • Documentation update
  • Tests
  • Other

Related Issues

Checklist

  • I have performed a self-review of my code
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works

Summary by CodeRabbit

  • Documentation
    • Complete overhaul of README into a modern, TypeScript-focused docs site with centered header and updated badges
    • Added structured navigation and new sections (Quick Start, Features, API Reference, Docker, Real‑World Usage, Roadmap)
    • Expanded API docs with explicit method signatures, TypeScript examples, option tables, and notes on paging/rate limits
    • Reworked contribution, testing, license, privacy, and deployment guidance

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Dec 2, 2025

Warning

Rate limit exceeded

@bartholomej has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 0 minutes and 16 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

📥 Commits

Reviewing files that changed from the base of the PR and between 913106a and 6ea8c58.

📒 Files selected for processing (1)
  • README.md (6 hunks)

Walkthrough

Comprehensive rewrite of README.md transforming it into a TypeScript-focused, navigation-rich documentation site with expanded examples, API reference, Docker/REST guidance, and revised contribution/privacy/license content; no code or exported API declarations were changed.

Changes

Cohort / File(s) Summary
Documentation Overhaul
README.md
Full content rewrite and restructuring: updated header and badges, centered layout, navigation/TOC, Features/Supported Platforms, Installation, Quick Start with TypeScript examples, expanded API reference (explicit method signatures, option schemas, mutual-exclusion notes), Docker and REST sections, real-world usage, updated roadmap/contributing/testing/privacy/license.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Documentation-only change; no code logic edits.
  • Verify TypeScript example syntax and that renamed option descriptions accurately reflect the public API surface.

Poem

🐇 I hopped through lines and polished each note,
Swapped plain bullets for TypeScript to quote,
Badges aligned and examples now bright,
A README refreshed, snug as a bite,
Hop, read, and share — documentation delight! 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description follows the required template structure and includes type of change selection and checklist completion, but the 'Description' section is minimal with only 'Better DX and styling in readme' which lacks detail about what was changed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately summarizes the main change: restructuring the README with TypeScript focus and improved documentation structure, which aligns with the extensive documentation overhaul described in the changeset.

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov-commenter
Copy link

codecov-commenter commented Dec 2, 2025

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.52%. Comparing base (776569e) to head (6ea8c58).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #69   +/-   ##
=======================================
  Coverage   99.52%   99.52%           
=======================================
  Files          28       28           
  Lines         630      630           
  Branches      143      143           
=======================================
  Hits          627      627           
  Misses          3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🧹 Nitpick comments (1)
README.md (1)

395-398: Hyphenate compound adjectives.

Lines 397 and 595 use "rate limiting" as a compound adjective before a noun. Per English grammar, these should be hyphenated as "rate-limiting".

Apply these diffs:

-397~ > ⚠️ **Rate Limiting Warning**: When fetching all pages, use appropriate delays...
+397~ > ⚠️ **Rate-Limiting Warning**: When fetching all pages, use appropriate delays...
-595~ - [ ] Server: Rate limiting helpers
+595~ - [ ] Server: Rate-limiting helpers
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 776569e and 68c141a.

📒 Files selected for processing (1)
  • README.md (6 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[uncategorized] ~397-~397: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e: ['epizoda', 'série'] }); ``` > ⚠️ Rate Limiting Warning: When fetching all pages, use...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~595-~595: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... for improved performance - [ ] Server: Rate limiting helpers ## 🛠️ Development ### Prereq...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[style] ~655-~655: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...ontributing Contributions are welcome! Please feel free to submit a Pull Request. ### How to Cont...

(FEEL_FREE_TO_STYLE_ME)


[style] ~664-~664: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...yarn test) 6. **Commit your changes** (git commit -m 'Add amazing feature') 7. **Push to the branch** (...

(AWESOME)


[style] ~701-~701: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ally can't. I have nowhere to store it. I don't even have a server database to st...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 markdownlint-cli2 (0.18.1)
README.md

11-11: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


13-13: Link fragments should be valid

(MD051, link-fragments)


75-75: Link fragments should be valid

(MD051, link-fragments)


513-513: Link fragments should be valid

(MD051, link-fragments)


629-629: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

Comment on lines +74 to +79
- [Docker Support](#-docker-support)
- [Development](#-development)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Correct Table of Contents link fragments.

Line 75 uses #-docker-support but should be #docker-support (remove the dash after hash). All emoji-prefixed headings auto-generate anchors by dropping the emoji and lowercasing, not by keeping a leading dash.

Apply this diff:

Committable suggestion skipped: line range outside the PR's diff.

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

75-75: Link fragments should be valid

(MD051, link-fragments)

🤖 Prompt for AI Agents
In README.md around lines 74 to 75, the Table of Contents links use fragment
anchors with an extra leading dash (e.g. "#-docker-support") that don't match
auto-generated emoji-prefixed heading anchors; update the TOC fragments by
removing the dash after the hash (e.g. change "#-docker-support" to
"#docker-support" and similarly for any other entries like "#-development" to
"#development") so the links point to the correct anchors.

@bartholomej bartholomej force-pushed the docs/readme branch 3 times, most recently from 913106a to 05da0c2 Compare December 2, 2025 17:35
@bartholomej bartholomej changed the title Docs. Enhanced readme Docs: Restructure README with TypeScript focus and improved documentation structure Dec 2, 2025
@bartholomej bartholomej force-pushed the docs/readme branch 6 times, most recently from e5765b8 to 2223322 Compare December 2, 2025 17:50
@bartholomej bartholomej merged commit dc5a4f4 into master Dec 2, 2025
2 checks passed
@bartholomej bartholomej deleted the docs/readme branch December 2, 2025 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants