Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

fix($parse): handle interceptors with undefined expressions#13373

Closed
lgalfaso wants to merge 1 commit intoangular:masterfrom
lgalfaso:issue-13367
Closed

fix($parse): handle interceptors with undefined expressions#13373
lgalfaso wants to merge 1 commit intoangular:masterfrom
lgalfaso:issue-13367

Conversation

@lgalfaso
Copy link
Copy Markdown
Contributor

When calling $parse with undefined as the expression and with an interceptor, then when the function is evaluated, then call the interceptor

Closes: #13367

When calling `$parse` with `undefined` as the expression and with
an interceptor, then when the function is evaluated, then call the
interceptor

Closes: angular#13367
@petebacondarwin
Copy link
Copy Markdown
Contributor

Nice one @lgalfaso - merging (with additional $compile test)

lgalfaso added a commit that referenced this pull request Nov 25, 2015
When calling `$parse` with `undefined` as the expression and with
an interceptor, then when the function is evaluated, then call the
interceptor

Closes: #13367
Closes: #13373
petebacondarwin added a commit that referenced this pull request Nov 25, 2015
@lgalfaso lgalfaso closed this in 4473b81 Nov 25, 2015
petebacondarwin added a commit that referenced this pull request Nov 25, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants