Foundation: 'as' Props

[JasonGore]

Revisit as props in Slot context.

• First Step
  • Start with support for instrinsic-only root elements.
• Reconcile the meaning of as props
  • Intrinsic components vs. React components
  • Root elements vs. subcomponents.
• Type Safety
  • Concern of intrinsic attributes not lining up
  • Could make string for use with getNativeProps for type safety
  • React Router case?
• This CodePen identified a scenario where an titleAs prop would be significantly simpler than the approach highlighted in the CodePen.
  • Should slots allow for as props somehow?
  • Should children in this instance be render components?
• Render JSX / Function as replacement
  • How would slot shorthand props be passed?
  • How would slot props objects be passed?
  • How could replacement get specialized props?
  • Could a customized title render function be encapsulated inside a new CollapsibleSection component that just takes in shorthand/props externally?

[JasonGore]

Resolved with #8754 via component slot option. as props are distinguished from component slot option in the following ways:

• as props are top level component props, not associated with slot options, and only affect the root slot implementation and can only be intrinsic elements.
• component slot options only apply to slots and can be React components or intrinsic elements.

[msft-github-bot]

🎉This issue was addressed in #8754, which has now been successfully released as @uifabric/fabric-website@v6.19.0.:tada:

Handy links:

• Release Notes
• Official NPM Release