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

Maintaining revalidator #128

Open
zeke opened this issue Sep 15, 2019 · 4 comments
Open

Maintaining revalidator #128

zeke opened this issue Sep 15, 2019 · 4 comments

Comments

@zeke
Copy link
Contributor

zeke commented Sep 15, 2019

Hello! I have been using this module for years. It's simple, it's useful, and it's stable. Thanks to everyone for working on it!

I noticed there's an accumulation of helpful pull requests, and that the package hasn't been published in five years. I'd like to help get some of these additions landed and start publishing new releases to npm. Would you be open to adding me as an owner of this repo, or the org? And the npm module? If so:

npm owner add zeke revalidator

Thanks for your consideration!

cc @indexzero @indutny @mmalecki @pksunkara 👋

@iamdiogo
Copy link

Could we have a reply here? @zeke made a good point, revalidator hasn't been updated since 2015 and there are great pull requests that could be given some attention.
It would be great if there was someone maintaining the package.

@indexzero @indutny @mmalecki @pksunkara

@zeke
Copy link
Contributor Author

zeke commented Mar 25, 2020

Sometime after opening this issue, I switched over to ajv because that seems to be one of the more popular and well-maintained JSON schema validators.

Using ajv I discovered that the schemata I'd been using with revalidator were not actually valid according to the latest JSON schema specification. I forget the exact details, but I think it had something to do with the required property used by revalidator.

I got many good years of use from revalidatorbut in the end it made more sense for me to switch to ajv. 🤷‍♂

@pksunkara
Copy link
Contributor

I can't do anything here because I lost access to this org when I left Nodejitsu back in 2013. I suspect it's the case with others too. @indexzero is the only one who can help this.

@indexzero
Copy link
Member

Been planning to deprecate this for some time along with a number of other packages that were important in their day but have had better alternatives come up over the years.

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

4 participants