Add BurgerAPI to the list of frameworks

[Isfhan]

No description provided.

[coderabbitai]

Walkthrough

Added a single documentation entry to README.md: a new Extensions > Frameworks item describing BurgerAPI, a Bun.js-native framework with file-based routing, middleware, Zod validation, and automatic OpenAPI generation.

Changes

Cohort / File(s)	Change Summary
Documentation update README.md	Inserted a new Frameworks entry for "BurgerAPI" under the Extensions section describing its file-based routing, middleware support, Zod validation, and automatic OpenAPI generation.

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	No pull request description was provided by the author. The evaluation criteria do not explicitly address the scenario of a completely absent description, creating ambiguity about whether this should be considered as failing the "related to changeset" requirement or passing the "not off-topic" standard. Since there is no descriptive content to evaluate against the criteria of being related, vague, generic, or unrelated, there is insufficient information to make a conclusive determination.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Add BurgerAPI to the list of frameworks" is directly related to and accurately summarizes the main change in the changeset. According to the raw summary, the modification adds a new entry for BurgerAPI to the Frameworks subsection under Extensions in README.md. The title is concise, specific, and clearly communicates what the primary change accomplishes, making it easy for teammates reviewing the commit history to understand the purpose of this update.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e767e66 and 2a818a0.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[grammar] ~88-~88: Use a hyphen to join words.
Context: ....com/isfhan/burger-api) - A modern, open source Bun.js-native framework with file...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (1)

README.md (1)

88-88: Entry verified as accurate and properly formatted.

The BurgerAPI entry is legitimate and well-documented. Repository verification confirms the project is an active, open-source Bun.js framework with all described features (file-based routing, middleware support, Zod validation, automatic OpenAPI generation). The hyphenation of "Bun.js-native" is correct, and the entry follows established formatting conventions.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9b6277f and e767e66.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[grammar] ~88-~88: Use a hyphen to join words.
Context: ....com/isfhan/burger-api) - A modern, open source Bun.js native framework with file...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (1)

README.md (1)

88-88: Entry is well-formatted and consistent with the list.

The new framework entry is properly formatted, includes a clear description of features, follows the markdown list convention used throughout the file, and is appropriately positioned. The GitHub link structure is correct. No blocking issues identified.