jwt VS uuid

// ./pkg/middleware/jwt_middleware.go package middleware import ( "os" "github.com/gofiber/fiber/v2" jwtMiddleware "github.com/gofiber/jwt/v2" ) // JWTProtected func for specify routes group with JWT authentication. // See: https://github.com/gofiber/jwt func JWTProtected() func(*fiber.Ctx) error { // Create config for JWT authentication middleware. config := jwtMiddleware.Config{ SigningKey: []byte(os.Getenv("JWT_SECRET_KEY")), ContextKey: "jwt", // used in private routes ErrorHandler: jwtError, } return jwtMiddleware.New(config) } func jwtError(c *fiber.Ctx, err error) error { // Return status 401 and failed authentication error. if err.Error() == "Missing or malformed JWT" { return c.Status(fiber.StatusBadRequest).JSON(fiber.Map{ "error": true, "msg": err.Error(), }) } // Return status 401 and failed authentication error. return c.Status(fiber.StatusUnauthorized).JSON(fiber.Map{ "error": true, "msg": err.Error(), }) }

I use Google's UUID package a lot. But every time I refer to it in a new package, the language server picks up https://github.com/gofrs/uuid instead of https://github.com/google/uuid and then complains that the gofrs package isn't in go.mod. I assume because it's the first alphabetically (though this seems like a huge supply chain security loophole).

Just store one single UUID as a token in a client's cookie (use https://github.com/google/uuid for ex), and associate that to a user ID (or anything else relevant in your case), and an expiry date for example

Depends on your needs I think, I generally just use github.com/google/uuid like /u/wowsux mentioned it supports v1 through v5 of the UUID spec.

And we are also going to use google/uuid to generate random uuids.

If you are using "github.com/google/uuid", try the following codes

You can see the same naming dilemma in many Go library implementations, i.e., where a package is used to organize functions related to a single a type (https://github.com/google/uuid) vs organizing code of related functionality (https://github.com/golang/go/tree/master/src/math).

Type inference is not perfect yet (especially for functional options). Also not being able to add type parameters to methods is a bit annoying (can be worked around using package-level functions) but besides that generics fit quite nicely into the library. If type inference gets better then I think I can even remove the hard dependency on github.com/google/uuid and let users use custom types for ids.

Learn how to create UUIDs: https://github.com/google/uuid