ICheeseknifeObserver: an activity implementing this interface will be notified about all event handlers being invoked#14
Open
csm101 wants to merge 5 commits intoMarcelBraghetto:masterfrom
Open
Conversation
…ins the name of the method violating the check (making it easier to locate the problem in the sources)
…exception indicating the name of the offending event handler instead of a NullReferenceException
…ore and after the execution of each event handler (useful automatically logging user actions, trace exceptions, avoid multiple invocations of the same OnClick handler)
… and added a small sample app for it.
… tabs instead of spaces
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added a sample app for it.
In this pull request you will find also some minor changes:
A note about ICheseknifeObserver.AfterCheeseKnifeEvent: it works perfectly (it gets fired exactly at the end of the execution of the method) when the method is a plain void (not async) method, but if the method is declared as "async void" it gets fired immediately. I managed to get it handled correctly, instead, if the method is declared as "async Task"