📄 CodeRabbit inference engine (CODING_STANDARDS.md)

**/*.{js,jsx,ts,tsx}: Use 2 spaces for indentation. No tabs, just spaces
Stick to single quotes for strings. For JSX/TSX attributes, use double quotes (e.g., )
Always add semicolons at the end of statements
No trailing commas
Always use parentheses around parameters in arrow functions, even for single params
For multiline constructs, put opening braces on the same line, and ensure consistency. Minimum 2 elements for multiline
No newlines inside function parentheses
Space before and after the arrow in arrow functions. () => {} is good
No space between function name and parentheses. func() not func ()
Semicolons go at the end of the line, not on a new line
Names for functions need to be concise and descriptive
Add in JSDoc comments to add more details to the abstractions if needed
Add in meaningful comments instead of obvious ones where complex code flow is explained properly

Files:

• packages/bruno-app/src/components/RequestTabs/index.js
• tests/utils/page/actions.ts
• tests/utils/page/locators.ts
• tests/collection/moving-requests/tag-persistence.spec.ts
• packages/bruno-app/src/components/RequestPane/Settings/Tags/index.js

⚙️ CodeRabbit configuration file

tests/**/**.*: Review the following e2e test code written using the Playwright test library. Ensure that:

• Follow best practices for Playwright code and e2e automation

• Try to reduce usage of page.waitForTimeout(); in code unless absolutely necessary and the locator cannot be found using existing expect() playwright calls

• Avoid using page.pause() in code

• Use locator variables for locators

• Avoid using test.only

• Use multiple assertions

• Promote the use of test.step as much as possible so the generated reports are easier to read

• Ensure that the fixtures like the collections are nested inside the fixtures folder

  Fixture Example*: Here's an example of possible fixture and test pair

  .
  ├── fixtures
  │   └── collection
  │       ├── base.bru
  │       ├── bruno.json
  │       ├── collection.bru
  │       ├── ws-test-request-with-headers.bru
  │       ├── ws-test-request-with-subproto.bru
  │       └── ws-test-request.bru
  ├── connection.spec.ts # <- Depends on the collection in ./fixtures/collection
  ├── headers.spec.ts
  ├── persistence.spec.ts
  ├── variable-interpolation
  │   ├── fixtures
  │   │   └── collection
  │   │       ├── environments
  │   │       ├── bruno.json
  │   │       └── ws-interpolation-test.bru
  │   ├── init-user-data
  │   └── variable-interpolation.spec.ts # <- Depends on the collection in ./variable-interpolation/fixtures/collection
  └── subproto.spec.ts
  

Files:

• tests/utils/page/actions.ts
• tests/utils/page/locators.ts
• tests/collection/moving-requests/tag-persistence.spec.ts

Learnt from: CR
Repo: usebruno/bruno PR: 0
File: CODING_STANDARDS.md:0-0
Timestamp: 2025-12-05T20:31:33.005Z
Learning: Use consistent patterns and helper utilities where they improve clarity. Prefer shared test utilities over copy-pasted setup code, but only when it actually reduces complexity

Applied to files:

• tests/collection/moving-requests/tag-persistence.spec.ts

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

Applied to files:

• tests/collection/moving-requests/tag-persistence.spec.ts

tests/utils/page/locators.ts (1)

• buildCommonLocators (3-106)

tests/utils/page/actions.ts (1)

• selectRequestPaneTab (715-715)