Closed philliphoff closed 8 years ago
Related to #78.
Would be interesting to see how responsive the UI feels with a large number of log messages. E.g.,500?
Would be interesting to see how responsive the UI feels with a large number of log messages. E.g.,500?
I experimented with a request that generated 1500 messages; the UI feels pretty responsive at that level. I think if we were to adopt Redux, we could probably do better as it makes it pretty easy to ignore re-renders for components not affected by the state change.
Great about the responsiveness. This LGTM. What needs to happen to merge this in?
Just waiting for @avanderhoorn to also sign-off.
After that one minor style change/revert, :shipit:
Allows the user to filter trace/log messages by level.
The "component model" (i.e. "view model") concept has been split into separate components, the model itself and optional state which can reside with the React component (UI) and persist across models. (This enables the filter selection to be "sticky" as the user switches between requests, making comparisons of logs easier.)
The styling of the tab has also been updated to match the latest redlines.