Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Android] Change null returns for exceptions to avoid ambiguity #2715

Conversation

almedina-ms
Copy link
Contributor

Adds AdaptiveFallbackException to signalize an element couldn't be rendered avoiding the use of null as it may be ambiguous for external developers

How verified

The test cards we have were run and this is the output

Deep fallback

Screenshot_19700121-222528

ActionFallback

Screenshot_19700121-222542

}
}
}
}
else if (renderArgs.getAncestorHasFallback())
{
// There's an ancestor with fallback so we throw to test it
Copy link
Member

@paulcam206 paulcam206 Apr 18, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we throw to trigger it rather than test it, right? #Resolved

@almedina-ms almedina-ms merged commit 05b1f50 into master Apr 18, 2019
@almedina-ms almedina-ms deleted the user/almedina-ms/AndroidChangeBadRenderNotificationToException branch May 2, 2019 22:03
rankush pushed a commit to rankush/AdaptiveCards that referenced this pull request May 8, 2024
…osoft#2715)

* Fallback with exceptions v1

* Fix bugs in previous version and add more descriptive details to exception

* Update comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants