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
What platform is your issue or question related to? (Delete other platforms).
UWP
Details
Currently IAdaptiveCardElement has a MeetsRequirements() method on it to determine whether the element meets its requirements. For our known types, a single implementation exists in the base class that is used by all elements. For custom types, however, defining the requirement handling this way requires custom type developers to provide their own implementation of MeetsRequirements for their type.
To address this, we should change the MeetsRequirements function to a Requirements property which simply contains the requirements. We can then run our logic on that property to determine if it meets the requirements, removing the need from third party developers to understand and re-implement that logic in their own types.
The text was updated successfully, but these errors were encountered:
RebeccaAnne
changed the title
[UWP][Fallback Requirements] Change requirements handling from a function to a property
[UWP/Shared Model][Fallback Requirements] Change requirements handling from a function to a property
Aug 28, 2019
RebeccaAnne
changed the title
[UWP/Shared Model][Fallback Requirements] Change requirements handling from a function to a property
[UWP][Fallback Requirements] Change requirements handling from a function to a property
Aug 28, 2019
Platform
What platform is your issue or question related to? (Delete other platforms).
Details
Currently
IAdaptiveCardElement
has aMeetsRequirements()
method on it to determine whether the element meets its requirements. For our known types, a single implementation exists in the base class that is used by all elements. For custom types, however, defining the requirement handling this way requires custom type developers to provide their own implementation ofMeetsRequirements
for their type.To address this, we should change the
MeetsRequirements
function to aRequirements
property which simply contains the requirements. We can then run our logic on that property to determine if it meets the requirements, removing the need from third party developers to understand and re-implement that logic in their own types.The text was updated successfully, but these errors were encountered: