Ravi van Rooijen

To be honest I didn't think about that, of course that's a way better solution (in my defense, it was very late...) I have implemented this new system now.

@vitaly-t https://github.com/SweetIQ/schemats/pull/81#issuecomment-510185054

I think it'd be great if someone stepped up to maintain a fork of this project. It's very useful and has a lot of potential, but there are a few...

I think @evdhiggins made a fork (with useful changes) too (including copying my camel caseing PR 😉 ). ([Link for convenience](https://github.com/vaultdairy/schemats))

@evdhiggins Glad I could be of help! Just out of curiosity, what are the differences between my implementation and yours?

It might be a good idea to collect all useful PR's and forks currently existant that could be merged into the new "active" fork.

I'd love to contribute to this new fork! I think we should compose a list of all useful forks/PR's/issues that should be transferred to the new "fork"/version. I already have...

> I'm not sure if I would advocate for a renaming of the codebase (as it's still the same tool), but if this was necessary I would recommend a subtle...

That's unfortunate. Of course if we can publish to npm under the same name we can easily change all links to the new organization to direct any new users to...

The command line probably wouldn't be necessary because you can create PR's from other people's forks (unless I'm missing something here...)