How to reorder scope / repl variable expansion to have important data at the top

[andg-odoo]

Hello, been using Dap-view for a while now, great improvement over dap-ui but there has been one thing that has been bugging me that I've been wanting to ask and never got around to it. Within Dap-ui, when you expand a variable via scope or REPL, it will order variables (at least in python) with all public fields first and then all _ methods secondary. In Dap View it's just alphabetical which means for giant projects with tons of methods you have to scroll a very long distance just to see the variables you actually care about.

Here is an example below of the exact same variable expansion across the two systems:

Dap View:

Dap UI:

Thank you!

[igorlfs]

Hey,

it will order variables (at least in python) with all public fields first and then all _ methods secondary

Is this dap-ui's OOTB behavior? From taking a brief look at their source, it looks like this feature requires some configuration. (could be mistaken, haven't tested myself)

Dap View it's just alphabetical which means for giant projects with tons of methods you have to scroll a very long distance just to see the variables you actually care about

dap-view's "scopes" view is just an embedded nvim-dap widget. That means we can't easily change its behavior without first going through a change on nvim-dap's side, which is often more complex. However, lately, due to requests like this one (and a couple others), I've been thinking of reimplementing the scopes view "independently" (i.e., on dap-view's side). Initially, I just embedded the widget because I was a Lua n00b, but now I'm much more confident in my Lua skills.

I can give it a shot (and jump ahead and implement the sorting feature from dap-ui), but I'll need someone to "give it a spin" and that's where you would come in!

or REPL

AFAIK, dap-ui and dap-view should behave exactly the same on the REPL side. Both just embed the REPL from nvim-dap. Are you sure that's also the case with the REPL?

[andg-odoo]

Sorry for the late reply:

Is this dap-ui's OOTB behavior?

This was seen with no changes made to the config for dap-ui, which I do see is weird based on the code you linked, but it will be sorted as seen above, as well as have those sections for special and function variables.

I'll need someone to "give it a spin"

I'd be more than happy to, let me know when a branch is available and i'll take a look.

sure that's also the case with the REPL?

I was wrong, the repl is exactly the same, it's the watches and scopes views that appear this way.

[igorlfs]

Sorry for the late reply

No worries!

This was seen with no changes made to the config for dap-ui

That's... odd. I must have missed something...

...as well as have those sections for special and function variables

Just a note, these are also present on dap-view, they show up as the "last" variables with the "regular" (default) sorting.

let me know when a branch is available and i'll take a look

Here you go: #128

it's the watches and scopes views that appear this way

Initially, my plan is to enable this function only for the scopes. After reimplementing the scopes from scratch, I realized a lot of stuff can be simplified in the watches view. But don't worry, eventually this will also land there as well.

I'm excited to get your feedback! I put a lot of effort into reimplementing the scopes view, and from my tests the experience is basically flawless! Of course, it also needs some "real world" testing, which is what I'll be doing in the following days. But I would tremendously appreciate your thoughts on the new experience!

[andg-odoo]

It works great so far! I haven't seen any issues so far and I see it work properly for both watches and scopes. I didn't have to pass any function to `sort_variables` yet it still works so it seems like the default here is once again all that's necessary for it to work with python.

Thanks for the quick work :)

[igorlfs]

It works great so far!

Fantastic! It finally landed on main, hopefully everyone has the same experience as you ^_^

[igorlfs]

Closed by #128