[material_ui] Import of Material tokens v38.0.58

[elliette]

Import of tokens (see cl/944170221)

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

Test exemption: Import of generated code.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request updates the Material UI default token generation data by upgrading the schema version and refactoring numerous token classes to reference centralized typescale definitions rather than inline TypescaleStruct declarations. Feedback on the changes highlights a compilation error in banners_rich.dart due to a missing import and an incorrect reference to TokenTypescaleEmphasized, as well as an inconsistent typescale mapping in slider.dart where tracking and weight properties do not match the other label properties.

[gemini-code-assist]

Import typescale_emphasized.dart to resolve the reference to TokenTypescaleEmphasized used for titleTextType.

Suggested change

	import 'typescale.dart';
	import 'typescale.dart';
	import 'typescale_emphasized.dart';

[gemini-code-assist]

emphasizedBodyMedium is defined in TokenTypescaleEmphasized (from typescale_emphasized.dart), not TokenTypescale. Referencing it on TokenTypescale will cause a compilation error.

Suggested change

	static const TypescaleStruct titleTextType =
	TokenTypescale.emphasizedBodyMedium;
	static const TypescaleStruct titleTextType =
	TokenTypescaleEmphasized.emphasizedBodyMedium;

[QuncCccccc]

Hmmm good catch... 3P MD website doesn't have banner. In Carbon, rich Banner text style for 3p doesn't have values.

[gemini-code-assist]

There is a mismatch in the typescale mapping for the value indicator label text. The font, line-height, and size properties are mapped to TokenTypescale.labelLarge, but the tracking and weight properties are mapped to TokenTypescale.bodyLarge. They should consistently use TokenTypescale.labelLarge to avoid unexpected styling issues.

Suggested change

	static const double valueIndicatorLabelLabelTextTracking =
	TokenTypescale.bodyLarge.letterSpacing;
	/// md.comp.slider.value-indicator.label.label-text.weight
	static const double valueIndicatorLabelLabelTextWeight =
	TokenTypescale.bodyLarge.fontWeight;
	static const double valueIndicatorLabelLabelTextTracking =
	TokenTypescale.labelLarge.letterSpacing;
	/// md.comp.slider.value-indicator.label.label-text.weight
	static const double valueIndicatorLabelLabelTextWeight =
	TokenTypescale.labelLarge.fontWeight;