Skip to content

Fix $injector to resolve lambdas #2337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 9, 2016

Conversation

rosen-vladimirov
Copy link
Contributor

@rosen-vladimirov rosen-vladimirov commented Dec 8, 2016

As the transpilation had been changed to ES6 instead of ES5, there is a problem, when $injector should resolve lambdas.
When they are transpiled to ES5, they are converted to functions. However in ES6 they are still lambdas and current annotate method does not work correctly.
Fix the regex that's used for the parsing and add unit tests for the failing cases.

@rosen-vladimirov rosen-vladimirov added this to the 2.5.0 milestone Dec 8, 2016
@rosen-vladimirov rosen-vladimirov self-assigned this Dec 8, 2016
As the transpilation had been changed to ES6 instead of ES5, there is a problem, when $injector should resolve lambdas.
When they are transpiled to ES5, they are converted to functions. However in ES6 they are still lambdas and current `annotate` method does not work correctly.
Fix the regex that's used for the parsing and add unit tests for the failing cases.
@rosen-vladimirov rosen-vladimirov force-pushed the vladimirov/fix-lambdas-resolve branch from 32b5328 to c91c090 Compare December 8, 2016 21:45
@Mitko-Kerezov
Copy link
Contributor

LGTM 👍

@rosen-vladimirov rosen-vladimirov merged commit 8419e85 into master Dec 9, 2016
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/fix-lambdas-resolve branch December 9, 2016 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants