Hi @isidorn
I've created a PR. Let me know if there's anything missing or any changes to do.
Thanks.

@pfongkye thanks a lot for this PR. I will review it in detail and test it out tomorrow

@pfongkye thanks for your PR, I tried it out and seems to work good. Here's my feedback:

• You are bringing back layout code for the shrink and grow of the Repl Filter, however the repl filter does not properly shrink and grow - it does not work with your changes. What I suggest is to remove this code completly from this PR and if you would like to tackle the shrink / grow issue please create an additional PR and test it out.
• So from the above this PR should only contain the Badge which shows the number of filtered items work
• Once you filter for some term that is nonexistent the debug console will be empty but the badge will not show anything. I suggest to show "showing 0 of N". That will make it more clear. And I suggest to also change that in problems view to be consistent

Thanks!

@isidorn
Thanks for the feedback.
I'll make the necessary changes and create another issue for the shrink/grow problem. I'll keep you updated.

Great thanks. Just ping me once it is ready for review again.

@isidorn friendly ping to let you know the PR is ready for review.
I created an issue for the layout: #107230

Looks great! Merging in and I will push some polish commits on top of this work.
Thanks a lot for your work!

Pushed some minor improvements via a47bf98

Pushed some minor improvements via a47bf98

@isidorn I like the refactoring since it's cleaner now. However, I noticed that a scenario might have been left out.

When you pause the debugger and begin to type in the filter, the badge will be updated. However, if you hit continue on the debugger, the badge will not be updated, showing x of n will remain the same even though there are more lines appearing.
I used the following listener for this scenario: this._register(this.tree.onDidChangeContentHeight(() => this.refreshReplElements(false))); but maybe there is a better solution.

@pfongkye great catch. I have tackled this via 8e82678