⚡ Bolt: Pre-compile Regex for Mock Rules#9
⚡ Bolt: Pre-compile Regex for Mock Rules#9google-labs-jules[bot] wants to merge 1 commit intomainfrom
Conversation
- Pre-compiles regex patterns in `loadMockSettings` to avoid recompilation on every request - Updates `mockRequestListener` to use cached `_compiledRegex` - Reduces overhead for Server Mode request interception
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
⚡ Bolt: Pre-compile Regex for Mock Rules
💡 What:
Moved the regular expression compilation logic from the
mockRequestListener(hot path) to theloadMockSettingsfunction (initialization/update path).🎯 Why:
The original implementation compiled a new
RegExpobject for every active mock rule on every single network request when Server Mode was enabled. This was an unnecessary O(n*m) operation (n=requests, m=rules) that wasted CPU cycles.📊 Impact:
🔬 Measurement:
Verified via code analysis and running the existing test suite (
npm test). The logic remains identical, just the execution time is shifted to the setup phase.PR created automatically by Jules for task 520261706603359735 started by @xkilldash9x