Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Is there an active Java implementation? #245

Closed
jmaister opened this issue Jan 29, 2022 · 5 comments
Closed

Question: Is there an active Java implementation? #245

jmaister opened this issue Jan 29, 2022 · 5 comments

Comments

@jmaister
Copy link

I would like to use cuid in a Java project. I've seen there is a link to a project, however, it is archived.

Is there any active Java implementation?

If not, I could implement it and keep it updated.

@ericelliott
Copy link
Collaborator

If it's not linked, I'm not aware of it.

@thibaultmeyer
Copy link
Contributor

thibaultmeyer commented Oct 21, 2022

Hello @ericelliott @jmaister,

I've uploaded my Java implementation of the CUID compatible with Java 8 and above. You can find it in this repos: https://github.com/thibaultmeyer/cuid-java.

It would be interesting to create an organization to gather all the implementations in the same place as well as the source of the web site. "usecuid" (like the website domain) is available, could be a good name for the organization. What do you think about this idea?

@ericelliott
Copy link
Collaborator

Open a PR and reference this issue number, and I'll merge into the list of CUID ports.

Organizations cost money to maintain (GitHub Free is missing crucial features like protected branches), so unless we get funding, I'm not going to create an org unless somebody wants to guarantee funding.

@thibaultmeyer
Copy link
Contributor

thibaultmeyer commented Oct 23, 2022

OK I will open a PR to reference this new java implementation.

EDIT: Just try on my organization (free plan), protection rule can be used (tested with "require CI success before merge" and "require a PR" rules). The use of roles defining the people/Teams allowed to write/read/only manage PR/... on each repository works very well too (like many open source projects that don't want to pay github).

EDIT 2: PR is open #268

@ericelliott
Copy link
Collaborator

Merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants