Skip to content
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

Eval? #3

Open
davidchase opened this issue Feb 3, 2014 · 4 comments
Open

Eval? #3

davidchase opened this issue Feb 3, 2014 · 4 comments

Comments

@davidchase
Copy link

I found your autocomplete via ngModules its pretty sweet! & easy to use..

But my question is, what was the reasoning behind using eval when you can just use bracket notation instead and achieve the same results instead of sprinkling eval around?

Thanks
-David

@toutpt
Copy link

toutpt commented Feb 4, 2014

+1 you should not use eval.

@stevenharman
Copy link
Contributor

From what I can tell, the eval allows arbitrarily long chains of "dot notation". If we had list comprehensions, or by brute-forcing a for loop, the same thing could be achieved by split('.')-ing and then using bracket notation.

@darylrowland
Copy link
Owner

Yeah I agree, had meant to remove the eval but completely forgot it was still in there. Will fix it tomorrow. Cheers guys.

Daryl.

Sent from my iPhone

On 4 Feb 2014, at 21:32, Steven Harman notifications@github.com wrote:

From what I can tell, the eval allows arbitrarily long chains of "dot notation". If we had list comprehensions, or by brute-forcing a for loop the same thing could be achieved by split('.')-ing and then using bracket notation.


Reply to this email directly or view it on GitHub.

@davidchase
Copy link
Author

Yeah I was just curious because in my implementation I subbed out the eval with bracket notation and all is well :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants