Skip to content
This repository was archived by the owner on Oct 22, 2021. It is now read-only.

Conversation

kasperlewau
Copy link
Contributor

Checking the name of the watchDelegate does not play well with a minified source. Checking the length of the given watchDelegate (the amount of parameters), we can rule out cases where we are not dealing with a oneTimeWatchDelegate.

A better solution to this problem has to be be out there, somewhere.

yuck


Closes #14

@kasperlewau kasperlewau force-pushed the fix/broken-notifications branch 2 times, most recently from e953164 to ed8e45d Compare October 28, 2015 21:46
@kasperlewau kasperlewau reopened this Oct 28, 2015
Checking the name of the given watchDelegate does not play well with a minified version of Angular. However, checking on the amount of expected arguments on the given watchDelegate we can rule out cases where we are not dealing with a oneTimeWatchDelegate.
@kasperlewau kasperlewau force-pushed the fix/broken-notifications branch from ffc85f1 to af33308 Compare October 28, 2015 22:03
@kasperlewau kasperlewau changed the title fix(dynamicWatcher): oneTimeWatch prototype existence check fix(dynamicWatcher): watchDelegate.length check Oct 28, 2015
kasperlewau added a commit that referenced this pull request Oct 28, 2015
fix(dynamicWatcher): watchDelegate.length check
@kasperlewau kasperlewau merged commit 2a4c0d7 into master Oct 28, 2015
@kasperlewau kasperlewau deleted the fix/broken-notifications branch October 28, 2015 22:05
@kasperlewau kasperlewau restored the fix/broken-notifications branch October 28, 2015 22:05
@kasperlewau kasperlewau mentioned this pull request Oct 28, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

1 participant