packages/bruno-app/src/components/Sidebar/SidebarSection/index.js (1)

69-74: Consider updating local state immediately for consistency.

The onClick handler updates only the context via setSectionExpanded(id, true) and relies on the useEffect (lines 20-23) to sync localExpanded. In contrast, handleToggle (lines 25-29) updates both localExpanded and the context immediately.

For consistency and to avoid potential UI lag, consider updating localExpanded directly:

🔎 Proposed refactor for immediate state update

 onClick={(e) => {
   e.stopPropagation();
   if (!localExpanded) {
+    setLocalExpanded(true);
     setSectionExpanded(id, true);
   }
 }}

tests/sidebar/section-auto-expand.spec.ts (3)

4-29: Use test.step to improve test readability.

Per coding guidelines, test.step should be used to organize test actions and make reports easier to read. Consider restructuring this test with steps like "Verify section is initially collapsed", "Click action button", and "Verify section expands".

🔎 Proposed refactor with test.step

 test('Clicking action button on collapsed section should expand it', async ({ page }) => {
-  // The api-specs section is collapsed by default (only collections is expanded)
-  // Find the api-specs section by its title
-  const apiSpecsSection = page.locator('.sidebar-section').filter({ hasText: 'API Specs' });
-
-  // Verify the api-specs section is initially collapsed (doesn't have 'expanded' class)
-  await expect(apiSpecsSection).not.toHaveClass(/expanded/);
-
-  // Verify section-content is not visible when collapsed
-  const sectionContent = apiSpecsSection.locator('.section-content');
-  await expect(sectionContent).not.toBeVisible();
-
-  // Click on the add button in the section-actions area
-  // This should trigger the auto-expand logic
-  const addButton = page.getByTestId('api-specs-header-add-menu');
-  await addButton.click();
-
-  // Close the dropdown by pressing Escape (we just want to test the expand, not the dropdown action)
-  await page.keyboard.press('Escape');
-
-  // After clicking an action, the section should be expanded
-  await expect(apiSpecsSection).toHaveClass(/expanded/);
-
-  // Verify section-content is now visible
-  await expect(sectionContent).toBeVisible();
+  await test.step('Verify API Specs section is initially collapsed', async () => {
+    const apiSpecsSection = page.locator('.sidebar-section').filter({ hasText: 'API Specs' });
+    await expect(apiSpecsSection).not.toHaveClass(/expanded/);
+    
+    const sectionContent = apiSpecsSection.locator('.section-content');
+    await expect(sectionContent).not.toBeVisible();
+  });
+
+  await test.step('Click action button to trigger auto-expand', async () => {
+    const addButton = page.getByTestId('api-specs-header-add-menu');
+    await addButton.click();
+    await page.keyboard.press('Escape');
+  });
+
+  await test.step('Verify section is now expanded', async () => {
+    const apiSpecsSection = page.locator('.sidebar-section').filter({ hasText: 'API Specs' });
+    await expect(apiSpecsSection).toHaveClass(/expanded/);
+    
+    const sectionContent = apiSpecsSection.locator('.section-content');
+    await expect(sectionContent).toBeVisible();
+  });
 });

Note: You'll need to move locator declarations to be accessible across steps or redeclare them as shown.

Based on coding guidelines: "Promote the use of test.step as much as possible so the generated reports are easier to read."

---

31-52: Use test.step to improve test readability.

Apply the same test.step pattern here to organize the test into logical sections: verify initial state, perform action, verify final state.

Based on coding guidelines: "Promote the use of test.step as much as possible so the generated reports are easier to read."

---

54-73: Use test.step to improve test readability.

This test would benefit from steps like "Collapse Collections section", "Click search action button", and "Verify section expands". This makes the test flow clearer in reports.

Based on coding guidelines: "Promote the use of test.step as much as possible so the generated reports are easier to read."

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Learnt from: naman-bruno
Repo: usebruno/bruno PR: 6407
File: packages/bruno-app/src/components/Environments/ConfirmCloseEnvironment/index.js:5-41
Timestamp: 2025-12-17T21:41:24.730Z
Learning: Do not suggest PropTypes validation for React components in the Bruno codebase. The project does not use PropTypes, so reviews should avoid proposing PropTypes and rely on the existing typing/validation approach (e.g., TypeScript or alternative runtime checks) if applicable. This guideline applies broadly to all JavaScript/JSX components in the repo.

Learnt from: CR
Repo: usebruno/bruno PR: 0
File: CODING_STANDARDS.md:0-0
Timestamp: 2025-12-05T20:31:33.005Z
Learning: Applies to **/*.test.{js,jsx,ts,tsx} : Add tests for any new functionality or meaningful changes. If code is added, removed, or significantly modified, corresponding tests should be updated or created