What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested
Additional environment details
- Chrome Version 108.0.5359.99 (Official Build) (64-bit)
- SPFx version v1.13
- Node.js version * 14.18.1 (Currently using 64-bit executable)
- etc
Issue description
A recent change to adaptive cards has rolled out to at least two of my tenants which removes the ability to override the template getter to customize a card view. We were doing this for cards rendered in the SharePoint experience and rendering a different OOTB card for Teams mobile. Clients are unhappy with OOTB design limitations. Is there a safe, advisable way to continue supplying a third party card view? I see the note on BaseCardView that third party card views should not inherit from that base class. Is there a best practice way to develop a third party card view?
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested
Additional environment details
Issue description
A recent change to adaptive cards has rolled out to at least two of my tenants which removes the ability to override the template getter to customize a card view. We were doing this for cards rendered in the SharePoint experience and rendering a different OOTB card for Teams mobile. Clients are unhappy with OOTB design limitations. Is there a safe, advisable way to continue supplying a third party card view? I see the note on BaseCardView that third party card views should not inherit from that base class. Is there a best practice way to develop a third party card view?