-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
Problem (one or two sentences)
I understand that the roo resolution for .roo folders and modes is either project or global. This is inconvenient in repos that are mono repo and with multiple tech and sub folders.
Each subfolder is potentially a workspace and this makes it tricky to setup. Often having duplicates to handle.
Is is a strict decision no to follow resolution strategies like nuget configuration or .editorconfig? That would enable big projects to have dedicated settings per workspace.
Context (who is affected and when)
This impacts projects in mono repos of substantial complexity and with different tech stack to manage efficiently and focused.
Desired behavior (conceptual, not technical)
Conceptually the workspace settings would be compiled by merging from local workspace walking up folders until hitting the global suer level settings
Constraints / preferences (optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear context and impact
Roo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status