If a haxelib.json file does not have a "contributors" field, haxelib crashes when processing it about haxelib HOT 5 CLOSED

For me this is working as expected... if "contributors" is missing, I get:

At least one contributor must be included

If it's a string and not an array, I get:

invalid type for contributors

In essence, Data.doCheck() seems to be functioning as expected for me. And apparently that's been in there since May 5th, so should definitely be in the final Haxe 3 release. Can somebody else test this?

from haxelib.

Deleted my previously erroneous statement.

In fact the version I have does have a check in doCheck for contributors. However, doCheck apparently is not being called.

The haxelib command that is crashing is "haxelib path foo" where foo is a haxelib with a haxelib.json that does not have contributors.

from haxelib.

Ah, makes sense. Is that haxelib installed using "git" or "dev" commands?
Or did you get it from the haxelib repo?
On 31 May 2013 08:04, "bji" [email protected] wrote:

Deleted my previously erroneous statement.

In fact the version I have does have a check in doCheck for contributors.
However, doCheck apparently is not being called.

The haxelib command that is crashing is "haxelib path foo" where foo is a
haxelib with a haxelib.json that does not have contributors.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-18716275
.

from haxelib.

The haxelib program was built from haxe source obtained by:

svn export -r 6586 http://haxe.googlecode.com/svn/trunk haxe

That version is from May 6.

Have you tried "haxelib path foo" for a foo with a deficient haxelib.json? It's not easy for me to try to reproduce with the latest haxe source as we import and built haxe in a cumbersome way.

from haxelib.

Yeah I think I understand the problem. I think the best solution will be
to get "path" to give more useful error messages by using doCheck(). The
previous assumption was that only libs installed via "haxelib" or "local"
had JSON checking in place, but now that "dev" and "git" do, it makes sense
to do the check when reading the file, not just when submitting to haxelib.

I'll try patch it tonight or tomorrow. Thanks for taking the time to
report :)

Jason

On Fri, May 31, 2013 at 8:30 AM, bji [email protected] wrote:

The haxelib program was built from haxe source obtained by:

svn export -r 6586 http://haxe.googlecode.com/svn/trunk haxe

That version is from May 6.

Have you tried "haxelib path foo" for a foo with a deficient haxelib.json?
It's not easy for me to try to reproduce with the latest haxe source as we
import and built haxe in a cumbersome way.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-18717070
.

from haxelib.