You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to migrate to fluent UI and is comparing different offering, including react and web component options. However it seems those two offers are not in sync. For example, the ChoiceGroup in react side allows image and icons as part of label: https://developer.microsoft.com/en-us/fluentui#/controls/web/choicegroup and that particular control is used as official sample in Power platform components documentation: https://learn.microsoft.com/en-us/power-apps/developer/component-framework/tutorial-create-model-driven-field-component?tabs=after . I am trying to look for options to use fluent UI with web component instead of react, but notice that the RadioGroup web component seems lacking the feature in that tutorial, making it hard to create an web component flavor for that power apps control. Thank you
Library
Web Components (@fluentui/web-components)
Describe the feature that you would like added
We are trying to migrate to fluent UI and is comparing different offering, including react and web component options. However it seems those two offers are not in sync. For example, the ChoiceGroup in react side allows image and icons as part of label: https://developer.microsoft.com/en-us/fluentui#/controls/web/choicegroup and that particular control is used as official sample in Power platform components documentation: https://learn.microsoft.com/en-us/power-apps/developer/component-framework/tutorial-create-model-driven-field-component?tabs=after . I am trying to look for options to use fluent UI with web component instead of react, but notice that the RadioGroup web component seems lacking the feature in that tutorial, making it hard to create an web component flavor for that power apps control. Thank you
Have you discussed this feature with our team
No response
Additional context
If that feature can be implemented with existing components please provide an sample. Options to be configured like {"0":"ContactInfo","1":"Send","2":"Phone"} as shown in https://learn.microsoft.com/en-us/power-apps/developer/component-framework/tutorial-create-model-driven-field-component?tabs=after#description-of-props
Validations
Priority
None
The text was updated successfully, but these errors were encountered: