jsonapi-datastore
jsonapi-datastore copied to clipboard
Roadmap to 1.0
Hi guys,
There are a few things I'd like to do before releasing 1.0, and I would love your help to make sure everything is working:
- make sure the library works in most contexts (npm, bower, requirejs, browserify, angular, other?) ref: #5, #15, #16, #20
- move to TypeScript (and add transpyling to js)
- handle model deletion gracefully (mainly updating dependent relationships) PR: #28
- clean-up the
sync
interface (avoid thesyncWithMeta
, probably by offering ameta
method directly onJsonApiDataStore
, and also offering access toerrors
, and top-leveljson_api
, as per the spec) - handling links PR: #17
- improving docs/README (this is probably the most important)
- anything I might have missed – suggestions?
Any special reason why you want to move to TypeScript?
If it's about downstream convenience, then maybe just adding separate TypeScript and/or FlowType definitions files would be sufficient? That way you don't need the transpile step?
If it's about correctness when developing this project, might I suggest that you use FlowType comments? This keeps your code in pure JavaScript form without any transpile needed, and you still have option of adding a separate TypeScript file later.
Hi @jokeyrhyme – the move to typescript was mainly for correctness (though I'd much rather have browsers already have native support for TS than having to transpile...). Thanks for the FlowType suggestion! At the moment I do not have time to keep working on this project though (c.f. #32).
Hi @copasetickid – as mentioned here, I am sadly busy with other stuff at the moment, and not planning to do any JS work in the foreseeable future. I'd be very happy if someone stepped up as a new maintainer, and would happily provide guidance though.
Also, note that @niksy has been maintaining a fork of this: https://github.com/niksy/jsonapi-datastore
Ok, thanks for the update. I'd be open to maintaining it. I'll followup with in #32 to see if @niksy is open to collaborating together on this.
Hi @beaby - I'd like to take you up on that offer to be the new maintainer and would appreciate any guidance you have to provide. Do you have any free time coming up to chat further?
@copasetickid Great, let's wait for an answer from @niksy and have a chat altogether :+1:
@beauby sounds good. How much longer should we give @niksy to respond?
@copasetickid @beauby sorry for super late reply! :( I was very busy with various personal stuff and couldn’t dedicate time for this. If you’re still interested in working on this I would be glad to have a chat with you on how should we proceed with maintaining this useful package!
@copasetickid @beauby Any info on this?
@niksy Sorry for the lack of response, it was a busy time for last year and didn't have time to focus on this but I do now this year. I'm still interested in working on this so let me when you're free to chat about how we can move forward 😄
@copasetickid great! Any way I can contact you?
@niksy you can DM me https://twitter.com/copasetickid and we can chat and I'll give you my email address if you prefer that
@niksy Would still like to sync up and how we proceed with maintaining this library?
This has been going for some time unfortunately, and current situation in the world doesn’t help :(
@beauby @copasetickid can we get the ball rolling on this? Is there anyone else willing to step up for the project?
@copasetickid @beauby I’ve managed to fork this repository and create new and update version: https://github.com/niksy/jsonapi-data-manager/
I still think it’s better to work on original repository, so if you’re still interested, let’s discuss!
Hey @niksy, sure, please send me an email