Road towards relay compatibility about graffiti-mongoose HOT 13 CLOSED

@hekike @gergelyke Are you guys still developing this? Feels like the project is already dead before it even got off the ground...

from graffiti-mongoose.

hi @hardchor,

thanks for raising them! in the past weeks sadly we did not have the time that this project would deserve - could you help us out and send a PR with these?

from graffiti-mongoose.

I'm still at the crossroads which route to take:

• mongo - mongoose - graffiti or
• SQL - bookshelf - graphql-bookshelf

Before I invest any significant amount of time, how likely are you to continue this project, i.e. are you going to be using it in production apps or is it all still a bit in the air?

Also, mutation is a biggie - whilst not being a completely blocker for this ticket, not having mutations would certainly leave a big gap in any Relay integration. https://github.com/RisingStack/graffiti-mongoose/milestones/support%20mutation%20queries

from graffiti-mongoose.

We definitely want to use it in production applications - with that said, I would go for finishing up one graffiti adapter implementation first, this one, so we will have a reference when working with others, like bookshelf.

What do you think?

from graffiti-mongoose.

Totally agreed. Could have a bit of a catch up on Skype if you fancy.

from graffiti-mongoose.

in which timezone are you in? let's find a time which can work.

cc-ing in @hekike

from graffiti-mongoose.

GMT. Added you both to https://gitter.im/hardchor/graffiti

from graffiti-mongoose.

Given that the cursors are specified as opaque, I don't see why cursors and globally unique IDs need be the same. The global id could take the format of $collection:$_id and cursors could be $_id if indexing into a collection (data structured with parent references) or maybe even numerical offsets if indexing into a subelement of child references.

EDIT: globalIdField used here works nicely, wrapping the same information https://github.com/RisingStack/graffiti-mongoose/pull/27/files#diff-55c36325e001f1671db3cf8a5b686a2aR59

from graffiti-mongoose.

@parkan They are opaque, but as you already noted, encoded as a globally unique ID (just a simple base64 encoding)

from graffiti-mongoose.

We have added the node(ID!) endpoint and pagination support and we are currently working on the mutation support. The new version is published on npm (^3.0.0). Your feedback is welcome!

from graffiti-mongoose.

I guess we can close this, right?

from graffiti-mongoose.

I think we're still some way off full relay compatibility:

• viewer endpoint
• mutations

from graffiti-mongoose.

The viewer endpoint and mutations have already been added. Check out the latest version!

from graffiti-mongoose.