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

Better warning messages (partial file path) #88

Open
GoogleCodeExporter opened this issue Aug 23, 2015 · 1 comment
Open

Better warning messages (partial file path) #88

GoogleCodeExporter opened this issue Aug 23, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

The warnings are great:

   JS strict warning #157 in packages.js at line 230 ch 15 - anonymous function does not always return a value

but I don't know which "packages.js" file.

The file path should show a few levels.

e.g.

   JS strict warning #157 in .../bravojs/plugins/packages/packages.js at line 230 ch 15 - anonymous function does not always return a value

Original issue reported on code.google.com by christ...@christophdorn.com on 20 Sep 2011 at 11:17

@GoogleCodeExporter
Copy link
Author

The objective is to give the filename some context in terms of its parent 
directory(s) in case you have more than one JS file with the same name in your 
app. This is true for all warnings. I suggest 3 levels.

Original comment by christ...@christophdorn.com on 21 Sep 2011 at 12:16

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

No branches or pull requests

1 participant