Add generation of uuid V4 about faker HOT 5 CLOSED

Add your own for now.

from faker.

Well im open for it but adding another lib to implement all this crypto stuff is a bit overkill imo.

For 2.0 we improve the way we use extensions so i guess the best way there would be to create an extension that has a dependency on the ramsey uuid lib. We do not want this from core point of view but duplicating stuff again is also not right.

from faker.

Thank you for the feedback
ramsey uuid seems the way to go indeed.

I've also found some quite simple scripts here and there, like in the PHP doc but i don't know how reliable they are and if the mt_rand usage would fit with faker

public static function v4() {
    return sprintf('%04x%04x-%04x-%04x-%04x-%04x%04x%04x',

      // 32 bits for "time_low"
      mt_rand(0, 0xffff), mt_rand(0, 0xffff),

      // 16 bits for "time_mid"
      mt_rand(0, 0xffff),

      // 16 bits for "time_hi_and_version",
      // four most significant bits holds version number 4
      mt_rand(0, 0x0fff) | 0x4000,

      // 16 bits, 8 bits for "clk_seq_hi_res",
      // 8 bits for "clk_seq_low",
      // two most significant bits holds zero and one for variant DCE1.1
      mt_rand(0, 0x3fff) | 0x8000,

      // 48 bits for "node"
      mt_rand(0, 0xffff), mt_rand(0, 0xffff), mt_rand(0, 0xffff)
    );
  }

I can also easily build a small provider for my app for the moment

from faker.

Indeed. Lets stick with this approach since if you look at the total installs and stars and such this is the way to go. Its a simple lib and atleast we know that they are valid at that point (crypto stuff)

I will note it down for a possible extension for v2 though!

from faker.

Lets stick with this approach

Sorry i'm not sure i got your point here: did you mean add a simple function in v1 or build my own ?

from faker.