Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This has been annoying the heck out of me for the last months
All the time, the default level of 3 for the other tabs (not Variables, which is already 5) is usually never enough, especially for session
etc
Fun fact: current level 3 doesnt even show content of Profile, so the count seems to be cut off already on level 2...
For now I always have to either
not being able to trust debug kit to give me the details after clicking through the tree of elements only to find
[maximum depth reached]
So I recommend we default to 5 here in general, and allow the other tabs to be configured as well.
I on purpose used a different key, as VariablesPanel is sure different as it contains really a LOT of data, compared to the others, So keeping that one at 5 while allowing the others to be safely used on e.g. 8 makes sense to me.