Support for relay global ids about graphql-sequelize HOT 6 CLOSED

Why would you want _id in this case?

from graphql-sequelize.

I guess the _id is optional. I use it because I have some legacy code that hits REST endpoints from the front-end, which require the real id.

from graphql-sequelize.

Alright, i would be willing to accept a PR that offers a map option to attributeFields that renames fields defined in a key: rename map.

from graphql-sequelize.

What about built-in relay support that does the globalIdField part for you?

from graphql-sequelize.

I think i discussed this with @brad-decker but there was some argument against it.
But yeah a globalId: true (suggestions welcome) argument or similar that generates a globalIdField on the Model.name would be fine with me (i could use that actually).

from graphql-sequelize.

I'm fine with providing an argument to the attributeFields function to swap out the typical id in generation in favor of globalid. Just to note that the globalIdField parameter will be the name of the model which is the typical behavior that we are all implementing anyways. Good idea. 👍

from graphql-sequelize.