[Inconsistency] Parse failures for a given property should not fail the entire card

[RebeccaAnne]

Platform

What platform is your issue or question related to? (Delete other platforms).

• .NET HTML
• .NET WPF
• Android
• iOS
• JavaScript
• UWP
• Validation

.NET WPF and .NET HTML do need verification.

• Validating this task can be extensive, so added a task of developing validation procedure that can be used across the platforms.

Details

Currently the shared model platforms fail parsing of the entire card in the case that there is a parse error in any property. JavaScript on the other hand, drops only the failing element, returning a warning and continuing to parse. This issue tracks updating all platforms to behave consistently with JavaScript.

Required Properties List

This is not extensive list and will grow eventually to include all required properties.

• url in BackgroundImage
• Text in TextBlock; [Desktop vs Mobile][Platform Inconsistency] TextBlock with no text property #4478, [Android][Rendering] [Rendering breaks when empty string is given in TextBlock] #4801, [.NET] Excess spacing in empty text blocks #4305
• Column; [MS Teams][Rendering] [Empty Column results in complete rejection of json] #4297
• Facts in FactSet; [Android][Inconsistency between desktop and android] [Cards containing facts with empty title do not render] #3949, [iOS-Android-UWP][Parity Issue - Fact Set] [Card with empty factSet does not render on iOS but renders on other platforms] #4136

Shared Model

• String; tracked by [All][Consistency] Shared model should not throw exceptions for invalid adaptive cards #4834
  • URL in Background Image
  • Text in TextBlock; [Desktop vs Mobile][Platform Inconsistency] TextBlock with no text property #4478, [Android][Rendering] [Rendering breaks when empty string is given in TextBlock] #4801, [.NET] Excess spacing in empty text blocks #4305
• Array; tacked by [All][Consistency] Parsing Array Should Not Throw Exceptions #4837
  • Column; [MS Teams][Rendering] [Empty Column results in complete rejection of json] #4297
  • Facts in FactSet; [Android][Inconsistency between desktop and android] [Cards containing facts with empty title do not render] #3949, [iOS-Android-UWP][Parity Issue - Fact Set] [Card with empty factSet does not render on iOS but renders on other platforms] #4136

Logging

All parsers and renders should be able to log Parse Error when required properties are missing, and Renderer Warnings when encountered adaptive elements with missing required properties.

Parser Error

• .NET HTML
• .NET WPF
• Android
• iOS
• JavaScript
• UWP

Render Warning

• .NET HTML
• .NET WPF
• Android
• iOS
• JavaScript
• UWP

[ghost]

Hi @RebeccaAnne. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions.

[shalinijoshi19]

@jwoo-msft something to look into driving once you are back as part of the Inconsistency workstream! Thanks

[shalinijoshi19]

@jwoo-msft what's the POA on this one?

[RebeccaAnne]

Tracking this work via Epic #6015 and it's corresponding sub tasks.