Add support for the rest of sequelizeTypes about graphql-sequelize HOT 7 CLOSED

It's really just figuring out what they should map to i suppose.
I wanted to do JSONB but the closests is GraphQLObjectType and that needs a subset of fields, so you'd really look to define subfields for the JSONB which Sequelize doesn't support atm (but we've talked about doing sub schemas), we did something similar for VIRTUAL to support returnType to make VIRTUAL work with GraphQL.

ENUM should probably just map to a GraphQLString? That should be a trivial fix.

from graphql-sequelize.

I'll have to think about JSONB but ENUM should probably map to the GraphQLEnumType

from graphql-sequelize.

Oh yeah if there's an GraphQLEnumType definitely map to that.

from graphql-sequelize.

I can get a pull request in to add GraphQLEnumType support.

As for JSONB I'm not seeing any real way to do it unless Sequelize supports sub-schemas. The fields have to come from some where. One options that might work is adding a field to the options parameter that can define field values, like:

const fields = {
  data: {
    name: GraphQLString,
    id: GraphQLInt
  }
}

attributeFields(Model, { fields: { data: fields }}

But I don't know, there doesn't seem to be any advantage using that over just using exclude and defining the properties yourself and merge with _.assign

from graphql-sequelize.

#15 adds support for ARRAY and ENUM, though JSONB is still not supported yet.

from graphql-sequelize.

@aweary Sequelize doesn't support sub schemas at the moment.

from graphql-sequelize.

JSONB will have to be solved with exclude + custom type at the moment

from graphql-sequelize.