-
Notifications
You must be signed in to change notification settings - Fork 18
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
Find a new name for this project #20
Comments
Unfortunately it looks like Here's a couple suggestions that are available:
I kind of like |
Do any of these names float your goat @laurence-myers, or do you have any other names you like? |
Heya, I'm not sure if this will help in this case, but I made a thing that might help in coming up with a new name. 🙏 Unfortunately, when searching for |
Hmm sorry about that. I think for om memory when you put in spaces it searches for 2 variations, e.g. “validation-decorators” and “validationdecorators”. The latter is available and most likely the tool is misreporting it. I’ll look into it tomorrow. |
FYI, the above bug with npm-name-finder.com has been fixed. |
I've got ahold of the The next step is working out when to migrate to the new name. I'd like to tackle some of the major v1 milestone tasks first:
|
Moved final step "Publish a deprecation notice to npm" for this issue into its own issue (#69). |
tsdv-joi
is not memorable, nor does it roll off the tongue. Let's rename the library, and go with the obvious option(seems it's already taken, let's find a new name).joi-decorators
The text was updated successfully, but these errors were encountered: