Replies: 5 comments
-
The challenge here is that editing the condition is just as expensive computationally as editing the log. I think we have two options at the moment:
|
Beta Was this translation helpful? Give feedback.
-
Agreed, @jasonLaster . I spoke with @jaril earlier and I think we can put this lower in our priority stack for now. Still important, but not as important the other projects we've got going on. |
Beta Was this translation helpful? Give feedback.
-
It would be nice to let users see information about at least some of the hits when there are a lot of them, e.g. have a dialog "This breakpoint has 3680 hits but we can only show 200 at a time, select the range of hits you're interested in" or something. I agree it's not a high priority for now. Eventually we'll be able to handle conditions more efficiently in the backend and be able to use them with breakpoints that are hit millions of times, but that's also not a priority right now. Regardless, the user should have options for dealing with breakpoints that are hit many times without having to set a condition. |
Beta Was this translation helpful? Give feedback.
-
Agreed. We now that we have API support for running an analysis on an arbitrary set of points we should be able to do that |
Beta Was this translation helpful? Give feedback.
-
March 22, 2022 update: We now have Focus Mode! That can be a big part of the messaging here. I have an item to address this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Right now, if a breakpoint has over 200 hits, we restrict editing the breakpoint. This includes the log message and the condition.
There are cases where the user bumps into our 200 hit limitation, and knows how to be more specific about which hits they're interested in. When that happens, they're stuck. They can't edit the condition.
This Replay has some good lines on script.js to add a breakpoint on to test this.
Examples
A1: Hovering on a line with <200 hits (the button is clickable)

A2: After clicking the button on a line with <200 hits

B1: Hovering on a line with >200 hits (the button is disabled)

Beta Was this translation helpful? Give feedback.
All reactions