-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
modify AnyFunction to include generator functions #131
modify AnyFunction to include generator functions #131
Conversation
The fix for the parsing error may be to remove |
@davidchambers that worked. thank you! |
Makefile
Outdated
@@ -35,6 +35,7 @@ lint: | |||
-- index.js | |||
$(ESLINT) \ | |||
--env node \ | |||
--env es6 \ | |||
--env mocha \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The order in which --env
values are provided isn't significant, but I like --env es6 --env node --env mocha
as language-version > engine > framework
seems like the appropriate hierarchy. I love to avoid making arbitrary decisions. :)
Also, please add --env es3
to the $(ESLINT) ... -- index.js
command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any preference to where the --env es3
should go in the -- index.js
command? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's put it first there too. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's what I thought :)
This looks great, Arsani! As a last step please squash the commits and $ git rebase 829cece41561c879b2ff040d1ed269f75ba72e2c^ --interactive
$ git push origin AnyFunction-IncludeGeneratorType --force While you're at it, I suggest shortening the commit message to match the pull request title: -modify the AnyFunction to include generator functions, by using typeofEq('function').
+modify AnyFunction to include generator functions It's advisable to avoid lines longer than 72 characters in a commit message. :) |
done! |
Very nice! The commit is not being mapped to your GitHub account. If this bothers you, you can fix the issue by telling GitHub about the email address you included in the commit, or by amending the commit to use the same email address you use on GitHub. If this doesn't bother you, I'll go ahead and merge. |
I made my email public on github.. are there any more steps I need to take? |
fixed the author and email on the commit.. |
@davidchambers Thanks again for all your help. |
Makefile
Outdated
@@ -27,13 +27,15 @@ README.md: index.js | |||
.PHONY: lint | |||
lint: | |||
$(ESLINT) \ | |||
--env es6 \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that this is es6
rather than es3
. Let's keep it as es3
to ensure that we don't accidentally sneak ES6 features into the source code (it's okay to use ES6 features in the test suite).
Please update the commit with git commit --amend
. You'll then need to use --force
when you push to your branch.
whoops... good catch. |
Using
typeofEq('function')
for the AnyFunction to include generator functions.Note: The test uses a generator function (
function*(x){...
) but that causes the es3 linter to report a parse error on the*
.. Is there any way to avoid this?