Skip to content

Commit ae2fafc

Browse files
committed
Initial commit
1 parent c9d4c25 commit ae2fafc

File tree

18 files changed

+2471
-2
lines changed

18 files changed

+2471
-2
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. iOS]
28+
- Browser [e.g. chrome, safari]
29+
- Version [e.g. 22]
30+
31+
**Smartphone (please complete the following information):**
32+
- Device: [e.g. iPhone6]
33+
- OS: [e.g. iOS8.1]
34+
- Browser [e.g. stock browser, safari]
35+
- Version [e.g. 22]
36+
37+
**Additional context**
38+
Add any other context about the problem here.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

.github/workflows/pr.yml

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
name: Pull request
2+
on:
3+
pull_request:
4+
branches:
5+
- main
6+
jobs:
7+
vet:
8+
name: Vet
9+
runs-on: ubuntu-latest
10+
concurrency:
11+
group: ${{ github.head_ref }}-vet
12+
cancel-in-progress: true
13+
steps:
14+
- name: Checkout
15+
uses: actions/checkout@v4
16+
with:
17+
ref: ${{ github.event.pull_request.head.sha }}
18+
- name: Setup asdf
19+
uses: asdf-vm/actions/install@v3
20+
- name: Install dependencies
21+
run: go mod download
22+
- name: Add asdf shims to PATH
23+
run: |
24+
echo "${HOME}/.asdf/shims" >> $GITHUB_PATH
25+
- name: Lint
26+
run: go vet ./...
27+
- name: Run tests
28+
run: go test -v ./... -bench=. -benchmem

.tool-versions

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
golang 1.19

CODE_OF_CONDUCT.md

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
jared@flexstack.com.
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Contribute
2+
3+
> A guide for contributing to `uuid`
4+
5+
## Getting Started
6+
7+
1. [Install asdf](https://asdf-vm.com/guide/getting-started.html) - A CLI tool that can manage multiple
8+
language runtime versions on a per-project basis
9+
10+
3. Clone the repo and open in VSCode
11+
12+
```sh
13+
git clone https://github.com/flexstack/uuid
14+
code uuid
15+
```
16+
17+
4. Install the project's dependencies
18+
19+
```sh
20+
asdf install
21+
go mod download
22+
```
23+
24+
## Development
25+
26+
Vet code
27+
```sh
28+
go vet ./...
29+
```
30+
31+
Run tests
32+
```sh
33+
go test -v ./... -bench=. -benchmem
34+
```
35+
36+
## Open an issue
37+
38+
If you find a bug or want to request a new feature, please open an issue.
39+
40+
## Submit a pull request
41+
42+
Before submitting a feature pull request, it is important to open an issue to discuss what you plan to work on to ensure success in releasing your changes.
43+
For small bug fixes or improvements, go ahead and submit a pull request without an issue.
44+
45+
1. Fork the repo
46+
2. Create a new branch (`git checkout -b feature/my-feature`)
47+
3. Make your changes
48+
4. Commit your changes (`git commit -am 'Add my feature'`)
49+
5. Push to the branch (`git push origin feature/my-feature`)
50+
6. Create a new Pull Request
51+
52+
## License
53+
54+
MIT

LICENSE

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
MIT License
22

3-
Copyright (c) 2024 FlexStack
3+
Copyright (c) 2024 FlexStack Contributors. All rights reserved.
44

55
Permission is hereby granted, free of charge, to any person obtaining a copy
66
of this software and associated documentation files (the "Software"), to deal

README.md

Lines changed: 57 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,58 @@
11
# uuid
2-
Faster v4 and v7 UUIDs in Go
2+
3+
Faster, more flexible v4 and v7 UUIDs in Go
4+
5+
## Features
6+
7+
- [x] Generate and parse v4 and v7 UUIDs
8+
- [x] Canonical, hash, and base58 encoding
9+
- [x] Select a default string format (i.e. base58, hash, canonical)
10+
- [x] SQL scanning and JSON marshaling
11+
- [x] The fastest UUID parsing available in Golang
12+
13+
## Installation
14+
15+
```bash
16+
go get github.com/flexstack/uuid
17+
```
18+
19+
## Usage
20+
21+
```go
22+
import "github.com/flexstack/uuid"
23+
24+
// Optionally set a default format
25+
uuid.DefaultFormat = uuid.FormatBase58
26+
27+
// Generate a new v4 UUID
28+
u := uuid.Must(uuid.NewV4())
29+
30+
// Generate a new v7 UUID
31+
u := uuid.Must(uuid.NewV7())
32+
33+
// Parse a UUID
34+
u, err := uuid.FromString("6ba7b810-9dad-11d1-80b4-00c04fd430c8")
35+
36+
// Parse a UUID from a byte slice
37+
u, err := uuid.FromBytes([]byte{0x6b, 0xa7, 0xb8, 0x10, 0x9d, 0xad, 0x11, 0xd1, 0x80, 0xb4, 0x00, 0xc0, 0x4f, 0xd4, 0x30, 0xc8})
38+
39+
// Scan a SQL UUID
40+
var u uuid.UUID
41+
err := db.QueryRow("SELECT id FROM users WHERE email = $1", email).Scan(&u)
42+
if u.IsNil() {
43+
// Handle nil row
44+
}
45+
```
46+
47+
48+
## Credit
49+
50+
This package is a fork of [github.com/google/uuid](https://github.com/gofrs/uuid) with the following changes:
51+
52+
- 2x improvement to `FromString`, `UnmarshalText`, and `UnmarshalJSON` performance
53+
- Adds base58 encoding.
54+
- Allows people to set a default format (i.e. base58, hash, canonical)
55+
- Scans nil UUIDs from SQL databases as nil UUIDs (00000000-0000-0000-0000-000000000000) instead of `nil`.
56+
- Fixes issue with [TimestampFromV7](https://github.com/gofrs/uuid/issues/128) not being spec compliant.
57+
- Removed v1, v3, v5 UUIDs.
58+
- Removed support for braced and URN string formats.

0 commit comments

Comments
 (0)