Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.86%. Comparing base (28bc599) to head (75a9446).
Report is 15 commits behind head on dev.

@@            Coverage Diff             @@
##              dev    #8363      +/-   ##
==========================================
+ Coverage   89.82%   89.86%   +0.03%     
==========================================
  Files         412      414       +2     
  Lines       11878    11913      +35     
  Branches     2364     2364              
==========================================
+ Hits        10670    10706      +36     
+ Misses        681      676       -5     
- Partials      527      531       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mckaragoz In the title of the PR you wrote HideNavigation but in the code I see HidePagination which I find quite an odd name for a property on a pager ;). I guess you wanted to name it HideNavigation really?

MudDataGrid is not completely compatible with MudPagination
(from discord)

Can someone explain my why and what it the benefit of using MudPagination in the PagerContent of DataGrid instead of the MudDataGridPager?
Or I'm missing some use case?
Also I'd like to see tests that content gets hidden / shown when the corresponding values are set for properties.

Can someone explain my why and what it the benefit of using MudPagination in the PagerContent of DataGrid instead of the MudDataGridPager?

MudDataGridPager can only navigate to previous or next page. But with MudPagination user can go to 5th page from 1st page directly. If a datagrid has 10 pages and you want to go 5th one, need to click next page button 4 times, which is really unnecessary.

A small bUnit test would be nice so we could safely merge it and not worry that it breaks in future for some reason.

A small bUnit test would be nice so we could safely merge it and not worry that it breaks in future for some reason.

Well how can i test this visual?

The only way is to check that the appropriate classes are applied or not applied. Should be a very simple test.

Any update on this?

The only way is to check that the appropriate classes are applied or not applied. Should be a very simple test.

And yes, this what I basically want.
Also it got a conflict now.

Added test here.

Look at #8594, we are doing away with negative properties. So please rename to ShowNavigation and ShowPageNumber. The default value of the parameter and all the invocations have to be inverted of course, like I did in my PR.

@henon should be done now.