Skip to content

fix: correct misspellings (occurred, environments, separator/separated)#7933

Open
renatograsso10 wants to merge 1 commit into
usebruno:mainfrom
renatograsso10:fix/typos
Open

fix: correct misspellings (occurred, environments, separator/separated)#7933
renatograsso10 wants to merge 1 commit into
usebruno:mainfrom
renatograsso10:fix/typos

Conversation

@renatograsso10
Copy link
Copy Markdown

@renatograsso10 renatograsso10 commented May 6, 2026

Summary

Small typo fixes in error messages, test descriptions, and CSS class names.

Changes

  • packages/bruno-electron/src/app/collection-watcher.jsoccuredoccurred
  • packages/bruno-electron/src/ipc/preferences.jsoccuredoccurred, environementsenvironments (one console error message had both typos)
  • packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js.item-seperator / .seperator.item-separator / .separator. Verified via git grep that no other file references these class names, so the rename is self-contained.
  • packages/bruno-lang/v2/tests/list.spec.js — test description: list item are not seperated by atleast one newlinelist items are not separated by at least one newline

Test plan

  • npx jest packages/bruno-lang/v2/tests/list.spec.js — 29 tests pass
  • git grep -nwE 'occured|seperator|seperated|environements|atleast' returns no remaining occurrences in packages/

Summary by CodeRabbit

  • Style

    • Fixed styling for collection items to correct separator behavior and appearance.
  • Chores

    • Corrected spelling in multiple error/log messages.
  • Tests

    • Added a validation test to ensure list items are properly separated.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 6, 2026

Walkthrough

This PR fixes several spelling mistakes across the codebase: CSS class selectors in a sidebar component, log messages in two Electron modules, and a test description. It also adds a new unit test asserting that list items on the same line are invalid.

Changes

Typo Fixes and Test Validation

Layer / File(s) Summary
Styling Correction
packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js
Renamed CSS selectors from item-seperator / .seperator to item-separator / .separator; added item-separator block with nested .separator.
Log Message Fixes
packages/bruno-electron/src/app/collection-watcher.js, packages/bruno-electron/src/ipc/preferences.js
Corrected misspellings in error messages: "occured" → "occurred" and "environements" → "environments".
Tests
packages/bruno-lang/v2/tests/list.spec.js
Fixed test description typo ("seperated" → "separated") and added a new test ensuring list items on the same line cause a parse failure.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • lohit-bruno
  • helloanoop
  • sid-bruno
  • bijin-bruno

Poem

Small typos brushed away with care,
Separators spelled right, logs now fair,
A test ensures two items can't share a line,
Tidy fixes — nothing more divine,
Code hums neater, one small shine. ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: correcting multiple misspellings across error messages, test descriptions, and CSS class names throughout the codebase.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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.

Copy link
Copy Markdown
Contributor

@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.

🧹 Nitpick comments (1)
packages/bruno-lang/v2/tests/list.spec.js (1)

191-201: 💤 Low value

Test description could be more precise.

The description "list items are not separated by at least one newline" is misleading — tag_1 and tag_2 are newline-separated in the fixture. The actual violation is tag_2 and tag_3 appearing on the same line. A clearer name would be 'should fail when two list items appear on the same line'.

✏️ Suggested rename
-      it('should fail when list items are not separated by at least one newline', () => {
+      it('should fail when two list items appear on the same line', () => {
🤖 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 `@packages/bruno-lang/v2/tests/list.spec.js` around lines 191 - 201, The test
description for the unit using parser(input) is misleading: update the it(...)
title from "should fail when list items are not separated by at least one
newline" to a clearer description like "should fail when two list items appear
on the same line" so it accurately reflects the failure condition in the test
that tag_2 and tag_3 are on the same line; locate the it(...) call in
list.spec.js and change only the string argument to the new wording.
🤖 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.

Nitpick comments:
In `@packages/bruno-lang/v2/tests/list.spec.js`:
- Around line 191-201: The test description for the unit using parser(input) is
misleading: update the it(...) title from "should fail when list items are not
separated by at least one newline" to a clearer description like "should fail
when two list items appear on the same line" so it accurately reflects the
failure condition in the test that tag_2 and tag_3 are on the same line; locate
the it(...) call in list.spec.js and change only the string argument to the new
wording.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 60675cd2-fb6a-45e7-b78d-919bc8901254

📥 Commits

Reviewing files that changed from the base of the PR and between f8bf146 and 3a7937b.

📒 Files selected for processing (4)
  • packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js
  • packages/bruno-electron/src/app/collection-watcher.js
  • packages/bruno-electron/src/ipc/preferences.js
  • packages/bruno-lang/v2/tests/list.spec.js

- packages/bruno-electron/src/app/collection-watcher.js: "occured" -> "occurred"
- packages/bruno-electron/src/ipc/preferences.js: "occured" -> "occurred", "environements" -> "environments"
- packages/bruno-app/.../CollectionItem/StyledWrapper.js: ".item-seperator" / ".seperator" -> ".item-separator" / ".separator" (no other refs to these CSS class names exist in the repo)
- packages/bruno-lang/v2/tests/list.spec.js: test description "list item are not seperated by atleast" -> "list items are not separated by at least" (29 tests still pass)
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 6, 2026

Tip

For best results, initiate chat on the files or code changes.

@renatograsso10 — Sounds good! The updated wording accurately reflects the actual violation (same-line items), and 29/29 passing confirms nothing broke. Nice clean fix overall. 🎉


If you found this review helpful, would you consider giving us a shout-out on X?

Thank you for using CodeRabbit!

Copy link
Copy Markdown
Contributor

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js (1)

118-126: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove the unused item-separator CSS rule or confirm it's intended for future use.

The CSS selector was corrected but no component in the codebase applies the item-separator class. The rule is dead code unless it's being reserved for future implementation. Either clean it up or document why it's needed.

🤖 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
`@packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js`
around lines 118 - 126, The .item-separator CSS rule inside StyledWrapper (the
.item-separator selector and its nested .separator rule) appears unused; either
remove that rule from StyledWrapper.js to eliminate dead CSS, or if it's
intended, add a short comment above .item-separator explaining its purpose and
where/components will apply it (or add the .item-separator class to the relevant
component markup that should render the separator). Ensure you reference the
.item-separator and .separator selectors when making the change.
🤖 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.

Outside diff comments:
In
`@packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js`:
- Around line 118-126: The .item-separator CSS rule inside StyledWrapper (the
.item-separator selector and its nested .separator rule) appears unused; either
remove that rule from StyledWrapper.js to eliminate dead CSS, or if it's
intended, add a short comment above .item-separator explaining its purpose and
where/components will apply it (or add the .item-separator class to the relevant
component markup that should render the separator). Ensure you reference the
.item-separator and .separator selectors when making the change.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: df8a33d4-020a-4b32-b1ab-2fb92fba2113

📥 Commits

Reviewing files that changed from the base of the PR and between 3a7937b and c647bb9.

📒 Files selected for processing (4)
  • packages/bruno-app/src/components/Sidebar/Collections/Collection/CollectionItem/StyledWrapper.js
  • packages/bruno-electron/src/app/collection-watcher.js
  • packages/bruno-electron/src/ipc/preferences.js
  • packages/bruno-lang/v2/tests/list.spec.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant