-
Notifications
You must be signed in to change notification settings - Fork 16
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
Cuid2 stable version #7
Comments
I have been following that thread, and I haven't seen anywhere that they've said they expect a 1.0 release prior to pulling into prisma. If I missed something, please feel free to link me. Like I mentioned in that thread, the primary interface for generating an ID is not going to change at this point. I just want to think through some stuff like WASM targets and the customized CUID builder before committing to 1.0, since I take backwards compatibility rather seriously. The vast majority of Rust crates that most of us are using are not on 1.0 releases, so it's unclear to me why Prisma would need a 1.0 release. |
Unrelated to stabilizing the interface, but related to timelines, I am also currently in the process of moving states and have a hefty plate of stuff at my day job besides, so it may be hard to find time to play with this. That said, and just to be clear, I would consider to be stable the primary interface for generating IDs, which is |
Hi @mplanchard thanks for taking the time to reply to thoroughly! Sorry if I was coming off rude, didn't mean to be. Let me know if you need any assistance - I am gladly helping to discuss pro/cons and implementation details. We also invest in open source software ourselves, so could maybe also support with development. |
No worries, was just trying to make sure I was clear, since I'm not sure where the expectation about a stable release is coming from or what specifically prisma is waiting on |
Hello, wondering when to expect a stable version for cuid2 as it seems the guys over at prisma have that as a prerequisite for implementation.
Ref: prisma/prisma#17102
The text was updated successfully, but these errors were encountered: