There should be a strict form of $parse that is not forgiving

[AlexKeySmith]

It would be nice if $parse had an easy way of knowing if it was successful or not.

If for example the expression being passed to it had a typo, it will still return a meaningful object, but it's not particularly easy to know if it's returning a real function or a noop.

[lgalfaso]

Without some context, it is hard to know what you are talking about. The expression this.is.ok is just as good as an expression as this.is.not.good. Are you talking about having a way to disable the forgiving nature of angular expressions?

[AlexKeySmith]

Thanks @lgalfaso, yes I suppose I'm looking for either a stricter mode or something on the return which indicates if it was able to find the function or not.

I noticed whilst debugging through $parse that when it began to not find a function to map to, it assigned a noop and null as the params, it would be cool to expose that back out to the caller somehow. However I've not had a chance to look very deeply yet to gather how that could be achieved as the $parse code seems pretty complex.

Stepping through the debugger helped point out our typo bug.

I'm not necessarily sure if this is a feature request per-say or if there is a way already to spot the error.

Let's say I had the following abridged code:

<a on-button-press=" userActions.playPause(buttonName)"  button-name="PLAY_PAUSE">play/pause><a/>

If I were to make some typos by not using the correct case e.g:

<a on-button-press=" useractions.playpause(buttonname)"  button-name="PLAY_PAUSE">play/pause><a/>

Using parse to combine the on-button-press and button-name attributes would return a function ok, however it wouldn't map to the actual userActions.playPause("PLAY_PAUSE") that I was hoping for and it seemed tricky to know it had failed.

[lgalfaso]

The forgiving nature is needed in an asynchronous environment. The main issue with generating any warning when a function/field is not found is that it would be very verbose.

[AlexKeySmith]

Ah ok, if I understand it right... does it return a function that calls another function that may exist now or in the future?

Would it be possible to have a strict option that throws an exception perhaps? Rather than a warning?