Bruno P. Kinoshita

I also don't use that page, unless when I want to test some quick changes in small graphs. Will fix that pagination as that is definitely broken. Once that's fixed...

Synced code, updated IDE's (phew, that took a while), and reproduced with the example from issue description (thanks!). 

Still need to write tests, but here's a preview.    And while navigating through the rest of the UI, I noticed when clicking on the Dataset size count...

Added the same table to the info view now:  

Now just missing the unit/e2e tests, to be completed next spare time window :crossed_swords: :muscle:

Yup, that's another approach, common too. I was just wondering whether we should allow users to select any page number, but I think limiting it to a only a few...

The current coverage report works well, but the one provided by Vitest UI is like Surefire + Jacoco + a graph with the code, and only using Vitest (i.e. easy...

And of course writing tests I already found some bugs :bug: :sweat_smile: Going to fix and fix up the commits.

>Would it be better to have the graph names sorted so they appear in an predicable, albeit arbitrary, order? It can make it possible to guess how far through a...

> One of the recent dependency updates seems to caused git conflict on package.json and yarn.lock. I _think_ the second choice is correct except that `"vitest": "^1.3.1"` in this PR....