attributeFields should support `only` (being the opposite of `exclude`) about graphql-sequelize HOT 6 CLOSED

@mickhansen I would 👍 providing both options - Its pretty nice to have the exclude option if there's only one field you want to define yourself.

from graphql-sequelize.

@brad-decker We already have exclude, this issue is to add include also, not to remove exclude (i realize the wording might be ambigious though).

from graphql-sequelize.

Just so I'm clear, you mean to have include be an option where, when provided, graphql-sequelize only looks at those fields, but when it's not provided, it defaults to the current behavior of parsing all the fields (minus any excludes), correct?

from graphql-sequelize.

@aweary Correct. include might not be descriptive enough, perhaps only?

from graphql-sequelize.

Yeah my first thought would be that include would be including additional fields or something. only seems semantically correct. I can give this one a try later today.

from graphql-sequelize.

Yeah that is definitely one way to read it, it's definitely too ambigious then :)

from graphql-sequelize.