aeson-schema
aeson-schema copied to clipboard
Add to Stackage?
Hi, I would love to use this library but I'm hitting some inconsistent version constraints; could you add it to Stackage such that it will be possible to check its requirements against many other libraries ? Thank you!
I've addressed the required changes in #13
@ocramz I'm quite disinterested in maintaining this package as I don't use it at all anymore. I do plan to merge #13, fix travis and upload new version to Hackage but I'm not that interested in fixing up bounds all the time for new Stackage versions (which I also don't really use these days...).
However, I'm happy for you to add the package to Stackage under your own name. This is something that Stackage allows. I'd also be happy to add you to this GitHub repo and as a Hackage maintainer if you'd want to take more active role beyond that. Let me know.
@Fuuzetsu I would be willing to take over maintenance of this package.
@kozross I have added you on Hackage and sent GitHub invite.
Note however: https://github.com/Fuuzetsu/aeson-schema/pull/13#issuecomment-570501242
So maybe this package should no longer exist.
Glad @kozross stepped up for maintainership, I just have a couple patches to contribute for now. @Fuuzetsu I checked out aeson-schemas from LeapYear and while it is a very cool library it does not cover the same use cases as this one, namely checking a JSON struct against a JSON-schema spec; they introduced their own schema format.
@ocramz I see, I should have spent a little time reading what the package is about. Seems json-schema package is the same -- uses own schema thing. Thanks for checking.
@Fuuzetsu @ocramz Sorry to disappoint, but further discussions in my organization means that we're going to maintain our own copy. We've added a lot of modifications, and removed considerable functionality to suit our specific needs. The library will be available (soon!) and will credit @Fuuzetsu and the original author, but I don't think making such drastic changes to an existing library is preferable to starting a new one.
Sorry if this caused any confusion or disappointment.
@Fuuzetsu @kozross no worries! I'll bring this one up to date and cut a new release sometime soon.
@kozross No problem, happens all the time.
@ocramz Great, thank you.