Code search is a great tool, but it gives too much results. For debugging a problem in a live application a lot of the results are irrelevant. Most time i only want to see task templates, triggers and procedure templates. To find which task/trigger etc affects a certain table.
My suggestion would be:
add a checkbox: exclude non-assigned templates (active by default)
add a checkbox: exclude gui templates (this only shows code that would impact results, so only templates for tasks, procedures, subroutines, triggers (i might forget one here?)
New
Code Search more options for debugging
+10Personally, I’m not fully convinced this is the right direction. My impression is that Code Search is mainly used to investigate the impact of changes during development, rather than for the more specific scenario of debugging a live application that you describe.
Since impact can potentially be found in many different places, I’m a bit concerned that adding too many of these specific filter options could make the interface unnecessarily cluttered/complex for most developers.
I don’t know if you’re familiar with the following code search feature, but it might be helpful to you for organizing your search results for that session better.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.