Rename Icon path property to svgPath to fix type collision

[josemontespg]

Problem

The Icon component's name property accepts either a string (for standard icons) or an object with a path property (for custom SVG paths):

name: z.union([
  z.enum(ICON_NAMES),
  z.object({ path: z.string() }).strict(),
])

However, the Angular renderer uses a utility type to resolve properties that strips away shapes matching DataBindingType (which is defined as { path: string }). Because of this structural match, the { path: string } branch was being incorrectly excluded from the resolved type, leaving only the string enum and forcing developers to use as any casts when dealing with custom SVG paths.

Solution

This PR renames the property inside the object from path to svgPath. This breaks the structural match with DataBindingType and preserves the type in the union, allowing for proper type inference without forced casts.

name: z.union([
  z.enum(ICON_NAMES),
  z.object({ svgPath: z.string() }).strict(),
])

Changes

• Schema: Updated IconApi schema in web_core to use svgPath and added documentation description.
• Angular: Updated IconComponent to check for and use svgPath. Updated tests to use svgPath.
• React: Updated Icon component to use svgPath and correctly render an <svg> element instead of a ligature span.
• Lit: Updated Icon component to use svgPath and correctly render an <svg> element.
• Cleanup: Removed unnecessary as any casts in the Angular icon component.

[gemini-code-assist]

Code Review

This pull request renames the path property to svgPath across the Angular, React, and Web Core implementations of the Icon component to clarify that it expects SVG path data. While the property rename is consistent, the React implementation needs to be updated to correctly render an <svg> element when svgPath is provided, as it currently incorrectly treats the path data as a Material Symbol ligature. Additionally, the unintentional pinning of the dompurify dependency in the React package lock should be reverted, and a description should be added to the svgPath Zod schema for better documentation.

[ditman]

This is unfortunate, but makes sense. We should have a way to reserve these internal keywords at the protocol level, so this gets flagged earlier (and on custom components) (/cc @gspencergoog ?)

Also, IMO this is a technically breaking change, even though it never worked in the first place, it'll break cached responses; we should mark and release this as a breaking change.

[josemontespg]

This is unfortunate, but makes sense. We should have a way to reserve these internal keywords at the protocol level, so this gets flagged earlier (and on custom components) (/cc @gspencergoog ?)

I agree. Issue #1376 created to track

Also updated the changelogs to mark this as a breaking change.

[ditman]

There's some conflicts, but I think this is one of the last breaking changes that I see incoming; I'll use this as a break point to do a "next" release!