Skip to content

Conversation

olexale
Copy link
Contributor

@olexale olexale commented Jan 23, 2016

One more (and last) portion of removing async/awaits.

Additionally I propose one breaking change: when _currentPage is null DisplayAlert and DisplayActionSheet methods should not silently work. According to current source code PageModelCoreMethods constructor invokes from ResolvePageModel only and in that case _currentPage should never be null, but let's say that by some reason it is. When I'm getting result from DisplayAlert I do expect that I'm getting user response and application business logic will rely on this. But with current implementation it is not true, because framework returned some value (false in that case). As for me NullPointerException is better than incorrect business logic, so I propose to remove "_currentPage != null" condition.

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.

1 participant