Better warning messages (partial file path)

[Christoph Dorn]

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

Christoph

[Wes Garland]

Good point. Could you file this is as a bug?

Incidentally, you can turn the strict warnings off if you want, but I am quite fond of them. :)

Wes

--
Wesley W. Garland
Director, Product Development
PageMail, Inc.
+1 613 542 2787 x 102

[Christoph Dorn]

Wes Garland wrote:
> Good point. Could you file this is as a bug?

http://code.google.com/p/gpsee/issues/detail?id=88

> Incidentally, you can turn the strict warnings off if you want, but I
> am quite fond of them. :)

I like them too. Between nodejs, ringo, gpsee and jetpack (firefox
extension) the loader code is pretty "strict" by now!

Christoph

[Donny Viszneki]

What package (snicker) does packages.js come from? I realize you
express some degree of misunderstanding about which exact file is
described, but you probably know what software you're trying to run on
GPSEE.

It would help to know the context of the problem so I can better
understand exactly what improvement can be made and under what
circumstances this unhelpful output will occur. What exactly are you
doing to get this output and what other output are you getting?

Thanks :)

--
http://codebad.com/

[Christoph Dorn]

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.

Does that make sense?

Christoph

[Donny Viszneki]

Yes I'll try to evaluate and/or implement your recommendations when I
get a chance :)

On Tue, Sep 20, 2011 at 7:52 PM, Christoph Dorn

--
http://codebad.com/