Roadmap to 1.0

[beauby]

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: ES6 import with Browserify #5, Error: Uncaught ReferenceError: module is not defined #15, Add module existence check. #16, jsonapi-datastore does not work with requirejs #20
• move to TypeScript (and add transpyling to js)
• handle model deletion gracefully (mainly updating dependent relationships) PR: Removing objects from datastore #28
• clean-up the sync interface (avoid the syncWithMeta, probably by offering a meta method directly on JsonApiDataStore, and also offering access to errors, and top-level json_api, as per the spec)
• handling links PR: implemented _links property to hold link and relationship links while… #17
• improving docs/README (this is probably the most important)
• anything I might have missed – suggestions?

[jokeyrhyme]

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.

[beauby]

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).

[beauby]

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.

[beauby]

Also, note that @niksy has been maintaining a fork of this: https://github.com/niksy/jsonapi-datastore

[copasetickid]

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.

[copasetickid]

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?

[beauby]

@copasetickid Great, let's wait for an answer from @niksy and have a chat altogether 👍

[copasetickid]

@beauby sounds good. How much longer should we give @niksy to respond?

[niksy]

@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!

[niksy]

@copasetickid @beauby Any info on this?

[copasetickid]

@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 😄

[niksy]

@copasetickid great! Any way I can contact you?

[copasetickid]

@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