Block tip hint bar - #746
Conversation
|
Warning Review limit reached
Next review available in: 34 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
📝 WalkthroughWalkthroughThe application adds selectable Blockly block hints. Hints appear for selected blocks, support localized menu messages, default to disabled on narrow layouts, and use new tooltip and localization entries. ChangesBlockly block hints
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant User
participant Blockly
participant BlockHint
participant ToolsMenu
User->>Blockly: Select a block
Blockly->>BlockHint: Pass block tooltip
BlockHint-->>User: Display block hint
User->>ToolsMenu: Toggle block hints
ToolsMenu->>BlockHint: Update enabled state
BlockHint-->>User: Show or hide hint
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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: 5
🤖 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 `@locale/en.js`:
- Around line 1105-1107: In the locale definitions, add
block_hints_menu_location_ui to locale/es.js and every staged locale file that
lacks it, translating the message with each locale’s actual menu labels rather
than relying on the English fallback. Keep the existing show_block_hints_ui and
hide_block_hints_ui entries unchanged.
In `@locale/es.js`:
- Line 550: Update the Spanish tooltip string in the jump-related localization
entry to remove the claim that jumping moves the character forward with
momentum, while retaining the height, preserved running speed, physics
requirement, and keyword text.
In `@main/translation.js`:
- Line 203: Restore the Spanish keyword label to “Palabra clave” in the dynamic
translation entry in main/translation.js:203-203 and all affected tooltip
entries in locale/es.js:250-250, 396-411, 440-548, 551-586, 596-612, 622-633,
644-674, and 685-689, covering the listed set_speed, scene, model, animation,
camera, combine, connect, control, effects, events, materials, physics, sensing,
shape, sound, speech, text, math, transform, and XR rumble tooltips.
In `@style.css`:
- Around line 615-631: Update the .block-hint style to set pointer-events to
none, ensuring the overlaid hint does not intercept workspace selection or drag
interactions.
In `@ui/blockHint.js`:
- Around line 29-32: Update setBlockHintsEnabled to retain the most recently
selected block hint and render that stored hint when enabled changes back to
true, while preserving the existing hideBlockHint behavior when disabling hints.
Ensure the selected-block handling stores the hint even when hints are disabled
so re-enabling does not depend on another Blockly.Events.SELECTED event.
🪄 Autofix
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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 71e824b3-79c1-49e3-bc35-0946949f96dd
📒 Files selected for processing (16)
blocks/control.jsindex.htmllocale/de.jslocale/en.jslocale/es.jslocale/fr.jslocale/it.jslocale/pl.jslocale/pt.jslocale/sv.jsmain/blockhandling.jsmain/loading.jsmain/main.jsmain/translation.jsstyle.cssui/blockHint.js
|
@tracygardner I've requested your review for this one because it's not on the list, so feel free to not merge it if you don't like it. I went to start making a project and I was trying to figure out what one of the camera blocks did, so I thought it might be handy to be able to see the already existing tooltips more prominently. |
1 participant
Summary
Users are shown block hints on the top right corner of the workspace. These come from the locale files.
Desktop users are shown a one-time message on startup for how to hide the hints:
Mobile users are shown a one-time message for how to enable the hints:
Toggle setting appears on the tools menu
Summary by CodeRabbit
New Features
Localization
Bug Fixes