MudGlobal: Add more component defaults

[swatkinson]

Description

Updated the MudGlobal.cs file to include more component defaults for:
Button, Card, DataGrid, Grid, Link, Stack, and Tabs

How Has This Been Tested?

I've updated the Mudglobal defaults from the program.cs of the UnitTests.Viewer project, and verified that the changes were reflected in the components on the website visually. (Had to make changes to some component tests to make sure they didnt overwrite the global component defaults)

Button default changes, for example:

Type of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (fix or improvement to the website or code docs)

Checklist

• The PR is submitted to the correct branch (dev).
• My code follows the code style of this project.
• I've added relevant tests.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.82%. Comparing base (28bc599) to head (c6d8997).
Report is 543 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #9691      +/-   ##
==========================================
+ Coverage   89.82%   90.82%   +0.99%     
==========================================
  Files         412      406       -6     
  Lines       11878    12825     +947     
  Branches     2364     2476     +112     
==========================================
+ Hits        10670    11648     +978     
+ Misses        681      623      -58     
- Partials      527      554      +27     

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

[danielchalmers]

Great work! One small typo I noticed

[henon]

Did you overlook this or is there a reason for not including it in MudGlobal?

[henon]

I would love an automated unit test using reflection for this. The idea is as follows:

• Find all components, foreach component ...
  • check if there is a <ComponentNameWithoutMud>Defaults class (if not, do not fail for now, we can fail here later)
  • find all parameters of each component and foreach parameter ...
    • If there is a defaults class, check if the class contains a property with the same name as the parameter and if not fail the test
    • Check that changing the default in MudGlobal will affect the value of the parameter when instantiating the component

We already have an automated unit test that instantiates all components to make sure that they do not raise an exception. You could copy that test and reuse its logic for this.

[ScarletKuro]

What's the status of this? Are we waiting the test proposed by @henon?

[henon]

No it is not necessary and to be honest might be harder to do than I thought. Merging now.

[henon]

Thanks @swatkinson

[nicolassargos]

Hey! Nice job here. Do you plan to also add Variant ? That would be of great help.