docs: add Nano Banana 2 Lite model info to nano-banana-2 tutorial#1205
docs: add Nano Banana 2 Lite model info to nano-banana-2 tutorial#1205lin-bot23 wants to merge 1 commit into
Conversation
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughDocumentation updates across EN, JA, KO, and ZH locales introduce the Nano Banana 2 Lite model variant with pricing to the Nano Banana 2 tutorial (intro text, feature bullets, and model comparison table). Separately, the JA settings page updates terminology and removes sections, and the JA custom-nodes page revises text, reformats tables, and removes the プロンプト section. ChangesNano Banana 2 Lite Documentation (EN/JA/KO/ZH)
JA Settings and Custom-Nodes Sync
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
lin-bot23
force-pushed
the
feat/nano-banana-2-lite
branch
from
b962bc2 to
23872b7
Compare
|
Wrong file — should be pricing.mdx, not tutorial. Reopening with correct changes. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@ja/custom-nodes/js/javascript_objects_and_hijacking.mdx`:
- Around line 5-12: Keep the translation block metadata aligned with the actual
Japanese content in javascript_objects_and_hijacking.mdx: since the `## プロンプト`
section was removed, update the `translationBlockHashes` mapping to remove the
`Prompt` entry so the chunked translation contract matches the translated body.
Use the `translationBlockHashes` frontmatter block as the reference point and
ensure the remaining block hashes still correspond to existing sections only.
In `@ja/interface/settings/comfy.mdx`:
- Around line 17-23: The frontmatter translationBlockHashes still includes
entries for sections that no longer exist in the page body, which keeps the i18n
metadata out of sync. Update the frontmatter in the comfy.mdx settings page by
either removing the stale block hashes or restoring the matching content
sections so the declared blocks align with the actual markdown body. Use the
existing translationBlockHashes mapping and the deleted section names from Node
Search Box through Workflow to verify the final set matches the rendered
content.
In `@tutorials/partner-nodes/google/nano-banana-2.mdx`:
- Line 24: The MDX content in nano-banana-2.mdx uses em dashes in the product
descriptions, which violates the English MDX style guide. Update the affected
text in the same document, including the entries around Nano Banana 2 Lite and
the other matching line, and replace each em dash with a comma, colon, or a
second sentence while keeping the meaning and tone consistent.
In `@zh/tutorials/partner-nodes/google/nano-banana-2.mdx`:
- Around line 24-25: The text-rendering bullet in the partner-nodes Google Nano
Banana 2 tutorial uses the wrong noun for “marketing mockups,” so update the
wording in the markdown content to use a mockup-appropriate term such as “营销样稿”
instead of “营销模型”; keep the rest of the bullet unchanged and make the fix in the
translated description that mentions text rendering.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 0e499b01-49c4-4953-b722-96d02d070f35
📒 Files selected for processing (6)
ja/custom-nodes/js/javascript_objects_and_hijacking.mdxja/interface/settings/comfy.mdxja/tutorials/partner-nodes/google/nano-banana-2.mdxko/tutorials/partner-nodes/google/nano-banana-2.mdxtutorials/partner-nodes/google/nano-banana-2.mdxzh/tutorials/partner-nodes/google/nano-banana-2.mdx
| translationBlockHashes: | ||
| "LiteGraph": 33b00279 | ||
| "ComfyApp": 09c85456 | ||
| "LGraph": cef2473d | ||
| "LLink": 9d75d321 | ||
| "ComfyNode": 33354cbb | ||
| "Inputs and Widgets": 5aec68cf | ||
| "Prompt": 5df541b3 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Keep the Prompt block metadata in sync with the translated body.
The page still advertises a Prompt block in translationBlockHashes, but this PR removes the corresponding ## プロンプト section. That leaves the chunked-translation contract inconsistent and will make this file look perpetually out of sync.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@ja/custom-nodes/js/javascript_objects_and_hijacking.mdx` around lines 5 - 12,
Keep the translation block metadata aligned with the actual Japanese content in
javascript_objects_and_hijacking.mdx: since the `## プロンプト` section was removed,
update the `translationBlockHashes` mapping to remove the `Prompt` entry so the
chunked translation contract matches the translated body. Use the
`translationBlockHashes` frontmatter block as the reference point and ensure the
remaining block hashes still correspond to existing sections only.
| "Node Search Box": ced022f2 | ||
| "Node Widget": 58dc56bd | ||
| "Queue": c42d4492 | ||
| "Queue Button": c528e5f1 | ||
| "Validation": 306e3d1a | ||
| "Window": afe27bb3 | ||
| "Workflow": 55b8bcfa |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Remove or restore the deleted block entries in translationBlockHashes.
Node Search Box through Workflow are still declared in frontmatter even though those sections were removed from the page body. With the current i18n sync logic, this metadata/body mismatch will keep the translation drifting instead of truly in sync. Time to hash things out.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@ja/interface/settings/comfy.mdx` around lines 17 - 23, The frontmatter
translationBlockHashes still includes entries for sections that no longer exist
in the page body, which keeps the i18n metadata out of sync. Update the
frontmatter in the comfy.mdx settings page by either removing the stale block
hashes or restoring the matching content sections so the declared blocks align
with the actual markdown body. Use the existing translationBlockHashes mapping
and the deleted section names from Node Search Box through Workflow to verify
the final set matches the rendered content.
| - **Subject consistency** — Maintain character resemblance of up to 5 characters and fidelity of up to 14 objects in a single workflow | ||
| - **Configurable thinking levels** — Control how much the model "thinks" before generating (Minimal for fast exploration, High/Dynamic for complex layouts) | ||
| - **Precision text rendering and translation** — Generate accurate, legible text for marketing mockups, greeting cards, and localized assets | ||
| - **Nano Banana 2 Lite** — A budget-friendly option at $0.034/image with 1K resolution, perfect for high-volume image generation |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Let the em dashes dash.
Line 24 and Line 81 use —, which the English MDX style guide disallows. Replace them with a comma, colon, or a second sentence. As per coding guidelines, **/*.mdx: When editing English MDX documentation, avoid em dashes (—); prefer periods, commas, or colons instead.
Also applies to: 81-81
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/google/nano-banana-2.mdx` at line 24, The MDX content
in nano-banana-2.mdx uses em dashes in the product descriptions, which violates
the English MDX style guide. Update the affected text in the same document,
including the entries around Nano Banana 2 Lite and the other matching line, and
replace each em dash with a comma, colon, or a second sentence while keeping the
meaning and tone consistent.
Source: Coding guidelines
| - **可配置的思考级别** — 控制模型在生成前的“思考”程度（Minimal 用于快速探索，High/Dynamic 用于复杂布局） | ||
| - **精确文本渲染和翻译** — 为营销模型、贺卡和本地化资产生成准确、清晰的文本 |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Fix the noun in the text-rendering bullet.
Line 25 translates “marketing mockups” as 营销模型, which means “marketing models” instead of mockups. Mockup to model is a muddy puddle here; use a term like 营销样稿 or equivalent.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@zh/tutorials/partner-nodes/google/nano-banana-2.mdx` around lines 24 - 25,
The text-rendering bullet in the partner-nodes Google Nano Banana 2 tutorial
uses the wrong noun for “marketing mockups,” so update the wording in the
markdown content to use a mockup-appropriate term such as “营销样稿” instead of
“营销模型”; keep the rest of the bullet unchanged and make the fix in the translated
description that mentions text rendering.
1 participant
Summary
Based on ComfyUI PR #14693, which adds the "Nano Banana 2 Lite" model variant to the GeminiNanoBanana2V2 node.
Changes
Details
The Nano Banana 2 Lite is a budget-friendly option added to the same GeminiNanoBanana2V2 node: