example-go-restful-api
uuid
example-go-restful-api | uuid | |
---|---|---|
2 | 7 | |
13 | 1,519 | |
- | 1.9% | |
10.0 | 4.3 | |
over 1 year ago | 7 days ago | |
Go | Go | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
example-go-restful-api
uuid
-
satori uuid vs google uuid vs gofrs uuid ? which to use to generate uuid for enterprise coding standards
https://github.com/gofrs/uuid upto v5
-
Any way of blocking or preferring a package?
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).
-
cmackenzie1/go-uuid: library for generating version 4 (random) and version 7 (time-ordered) UUIDs
What makes this different than https://github.com/gofrs/uuid ?
-
Building web-based SaaS with Go as a solo entrepreneur. What should I be aware of?
Something to note is that all of this is still open source. Theoretically, someone can decide to fork SQLBoiler and add all the missing things, or send in a PR. A good example is that the current most popular uuid package. gofrs/uuid was forked from an unmaintained previously popular package.
-
Which UUID package do you use? and why?
You could also look at github.com/gofrs/uuid which includes support for v6 and v7 from the latest draft UUID spec. Personally I think the API for this library is nicer since the google one makes it difficult to tell what kind of UUID you are generating.
-
Example Golang RESTful API (Fully Containerized Local Development)
Postgres has native UUID support so don't use VARCHAR(36). Look at https://github.com/gofrs/uuid library, among others, to create uuid.
-
CVE-2021-3538 issued for latest release of github.com/satori/go.uuid
If you're using this library and are unsure what to do, a few of us maintain a fork of this library that has fixed these issues (and others): https://github.com/gofrs/uuid
What are some alternatives?
uuid - Go package for UUIDs based on RFC 4122 and DCE 1.1: Authentication and Security Services.
shortuuid - :mushroom: A generator library for concise, unambiguous and URL-safe UUIDs
go.uuid - UUID package for Go
fastuuid - FastUUID is a library which provides CPython bindings to Rust's UUID library
bob - SQL query builder and ORM/Factory generator for Go with support for PostgreSQL, MySQL and SQLite
go-nanoid - Nano ID for Go
sonyflake - A distributed unique ID generator inspired by Twitter's Snowflake
ksuid - K-Sortable Globally Unique IDs
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
go-uuid - A simple, stdlib only, go module for generating UUIDs (Universally Unique IDentifiers).
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
sqlc - Generate type-safe code from SQL