You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add .gitignore fallback support when .rooignore does not exist
- Fix .rooignore changes requiring VSCode restart by enhancing file watchers
- Fix clearIndexData() ignoring .rooignore by recreating services
- Remove duplicate ignore filtering in DirectoryScanner
- Update RooIgnoreController to handle both .gitignore and .rooignore patterns
- Add proper cleanup and service lifecycle management
Fixes#5656
@@ -200,14 +236,23 @@ export class RooIgnoreController {
200
236
}
201
237
202
238
/**
203
-
* Get formatted instructions about the .rooignore file for the LLM
204
-
* @returns Formatted instructions or undefined if .rooignore doesn't exist
239
+
* Get formatted instructions about the ignore file for the LLM
240
+
* @returns Formatted instructions or undefined if no ignore patterns exist
205
241
*/
206
242
getInstructions(): string|undefined{
207
-
if(!this.rooIgnoreContent){
208
-
returnundefined
243
+
if(this.rooIgnoreContent){
244
+
return`# .rooignore\n\n(The following is provided by a root-level .rooignore file where the user has specified files and directories that should not be accessed. When using list_files, you'll notice a ${LOCK_TEXT_SYMBOL} next to files that are blocked. Attempting to access the file's contents e.g. through read_file will result in an error.)\n\n${this.rooIgnoreContent}\n.rooignore`
return`# .gitignore (fallback)\n\n(The following is provided by a root-level .gitignore file that is being used as fallback ignore patterns since no .rooignore file exists. When using list_files, you'll notice a ${LOCK_TEXT_SYMBOL} next to files that are blocked. Attempting to access the file's contents e.g. through read_file will result in an error.)\n\n${this.gitIgnoreContent}\n.gitignore`
209
247
}
248
+
returnundefined
249
+
}
210
250
211
-
return`# .rooignore\n\n(The following is provided by a root-level .rooignore file where the user has specified files and directories that should not be accessed. When using list_files, you'll notice a ${LOCK_TEXT_SYMBOL} next to files that are blocked. Attempting to access the file's contents e.g. through read_file will result in an error.)\n\n${this.rooIgnoreContent}\n.rooignore`
251
+
/**
252
+
* Check if the controller is using .gitignore as fallback
253
+
* @returns true if using .gitignore patterns because .rooignore doesn't exist
0 commit comments