monicao/angular-uuid4

Angular service that generates UUIDs/GUIDs

angular-uuid4's Issues

Dist files not up to date with source

/angular-uuid4.js and angular-uuid4.min.js aren't up to date with /src/angular-uuid4.js. Most noticeable difference is the missing validate method, but there may be others.

Potentially invalid UUIDs

Some UUIDs are not validating based on the regex found here. http://stackoverflow.com/questions/7905929/how-to-test-valid-uuid-guid

Need to read the rfc http://www.ietf.org/rfc/rfc4122.txt and figure out if the if the issue is with the generator or with the regex.

From the tests:

Expected '180cb47a-9f51-48b3-e745-1503370f5c23' 
to match /^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$/i.

License of angular-uuid4 is incorrectly written in npm.

When I check the LICENSE.txt in this repository, angular-uuid4 is released under Apache-2.0.
However, in npm(https://www.npmjs.com/package/angular-uuid4), license information is written as MIT.

When the sun and moon are aligned on the 5th forte night the UUID is less random

Bump version in bower.json

Just FYI, bower throws a warning because the version number in bower.json is still 0.1.0

Consider publish the module at http://ngmodules.org/modules?query=uuid

at http://ngmodules.org/modules

:)

NPM module

There is no npm module of this package. Could you please publish it?

Generated UUIDs fail validation

Problem

Creating a UUID with uuid4.generate and validating that UUID with uuid4.validate sometimes fails.

Example code

Running in Karma/Jasmine:

var uuid = uuid4.generate();

expect(uuid4.validate(uuid)).toBe(true); // pot luck whether this passes

Sometimes passes, sometimes fails. No code or environment changes: The only difference is the generated UUID.

Replication

I've only been able to replicate this when running on PhantomJS running with Karma and Jasmine. I've tried replicating this in a real browser and was unable to replicate the issue (all generated UUIDs were valid).

I'm unsure of the limitations of PhantomJS and its implications on this library, or even if this is genuinely a compatibility issue with PhantomJS or something else entirely (though it seems like it is).