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

node: do not print SyntaxError hints to stderr - #7049

Closed
indutny wants to merge 1 commit into
nodejs:masterfrom
indutny:fix/gh-6920
Closed

indutny wants to merge 1 commit into
nodejs:masterfrom
indutny:fix/gh-6920

Conversation

@indutny

@indutny indutny commented Feb 5, 2014

Copy link
Copy Markdown
Member

Try embedding the ... ^ lines inside the SyntaxError (or any other
native error) object before giving up and printing them to the stderr.

fix #6920
fix #1310

Try embedding the ` ... ^` lines inside the `SyntaxError` (or any other
native error) object before giving up and printing them to the stderr.

fix nodejs#6920
fix nodejs#1310
@Nodejs-Jenkins

Copy link
Copy Markdown

Thank you for contributing this pull request! Here are a few pointers to make sure your submission will be considered for inclusion.

The following commiters were not found in the CLA:

  • Fedor Indutny

You can fix all these things without opening another issue.

Please see CONTRIBUTING.md for more information

@indutny

indutny commented Feb 5, 2014

Copy link
Copy Markdown
Member Author

Not sure if there any point in backporting it to v0.10, seems to be mostly a matter of style.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is because error was appended to the exception without \n as a first char, I think that generally it is a better approach.

@trevnorris

Copy link
Copy Markdown

Just a couple comments, but overall LGTM.

@indutny

indutny commented Feb 6, 2014

Copy link
Copy Markdown
Member Author

Thank you, landed in f1de13b

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants