Skip to content

Conversation

@evanlucas
Copy link
Contributor

This is to ensure that it is evaluated the same way it would be if it
were to be run by node or required.

Before, the following would pass if run by node, but fail if run via
the syntax check flag:

if (true){return} 

Now, this will pass the syntax check

Reported in #2411 (comment)

@bnoordhuis
Copy link
Member

LGTM if CI etc.

@evanlucas
Copy link
ContributorAuthor

@thefourtheye
Copy link
Contributor

LGTM

This is to ensure that it is evaluated the same way it would be if it were to be run by node or required. Before, the following would pass if run by node, but fail if run via the syntax check flag: if (true){return} Now, this will pass the syntax check PR-URL: nodejs#3587 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
@evanlucasevanlucas deleted the fixcheck branch October 29, 2015 18:10
@evanlucasevanlucas merged commit 08166cb into nodejs:masterOct 29, 2015
@evanlucas
Copy link
ContributorAuthor

Thanks, landed in 08166cb

@evanlucas
Copy link
ContributorAuthor

Do we want to try to get this into v5.0.0 too?

evanlucas added a commit that referenced this pull request Oct 29, 2015
This is to ensure that it is evaluated the same way it would be if it were to be run by node or required. Before, the following would pass if run by node, but fail if run via the syntax check flag: if (true){return} Now, this will pass the syntax check PR-URL: #3587 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
evanlucas added a commit that referenced this pull request Oct 29, 2015
This is to ensure that it is evaluated the same way it would be if it were to be run by node or required. Before, the following would pass if run by node, but fail if run via the syntax check flag: if (true){return} Now, this will pass the syntax check PR-URL: #3587 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
@jasnell
Copy link
Member

Landed in v4.x-staging in 7883294

@rvagg
Copy link
Member

possible semver-minor?

@evanlucas
Copy link
ContributorAuthor

I would think it's a bug fix, but if you feel differently, whatever works for me

@jasnell
Copy link
Member

I'd say bug fix.
On Oct 29, 2015 7:04 PM, "Rod Vagg" [email protected] wrote:

possible semver-minor?


Reply to this email directly or view it on GitHub
#3587 (comment).

@thefourtheye
Copy link
Contributor

+1 for bug fix.

@Fishrock123Fishrock123 mentioned this pull request Nov 6, 2015
evanlucas added a commit that referenced this pull request Nov 7, 2015
This is to ensure that it is evaluated the same way it would be if it were to be run by node or required. Before, the following would pass if run by node, but fail if run via the syntax check flag: if (true){return} Now, this will pass the syntax check PR-URL: #3587 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
@Fishrock123Fishrock123 mentioned this pull request Nov 11, 2015
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@evanlucas@bnoordhuis@thefourtheye@jasnell@rvagg