-
Notifications
You must be signed in to change notification settings - Fork 81
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
Plans for v1.0 Release #115
Comments
I'm currently working on a big redesign of the library in this PR: The main idea is to make the library much more maintainable while also giving people a mechanism to customise the generated IDs as much as they like. I can't say when I'll move out of the beta, but I'll feel a lot happier once this PR is merged! Of course, the beta suffix is relatively arbitrary as far as I'm concerned; all the code is provided under MIT licesnse, and you're free to fork/copy it into your projects if that will keep your teammates happy 😉 |
@andrewlock - now that #117 has been merged have you softened your stance on a non-beta release? |
Hey, I'm certainly considering it. The one outstanding issue is #111 - I had some ideas on how to resolve that, but it would require semi-breaking changes, so was hoping to fix that first. Unfortunately my initial PoC didn't really work out, so I'm at a bit of an impasse - I haven't found the time to revisit again yet, but I'd like to take one more shot at it to see if there's a nice solution. |
Hi did you have any plans for deploy a first v1.0 Release of this smart nuget package? Which of the issues are not ready for leave the beta state and goes to production ?
I personal want to use the package at current state, but my teammates told me that they have actualy a problem with integrate a beta version of a nuget package and they want to wait after we got an official v1.0 version from the feed.
Greetings Stefc
The text was updated successfully, but these errors were encountered: