is there a way to get the validation messages from mongoose to be displayed in the return result of the graphql query?
instead of the 'User Validation Error' message?
Hi guys, I have a productConnection within a category model, which is used to fetch the products belonging to that category. I am trying to add a filter in order ot filter by type, color, etc.. Having trouble figuring how out to do that. I have created a filter arg on the productConnection modeling the regexp one, which works if the query is
viewer { productConnection(filter: blah) { etc } }, but I am unable to put it on my embedded connection like so:query {
viewer {
category {
...
productConnection(filter: { nameRegex: 'blah' }) {
}
}
}
}
I just get
"unknown argument filter. did you mean after?"
Update: Seems like if I hardcode nameregex in the productConnection relation, it works:
CategoryTC.addRelation(
'productConnection',
() => ({
resolver: ProductTC.getResolver('connection'),
args: {
filter: (source) => ({
_operators: { // eslint-disable-line no-underscore-dangle
_id: { in: source.products }, // eslint-disable-line no-underscore-dangle
},
nameRegex: 'plat',
}),
sort: { sortOrder: 1 },
},
projection: { products: true },
}),
);
How can I then get the nameRegex val from the query on my jsx? I've seen examples where the entire
filter is in the query but I would rather keep the _id operator in the relation itself.
The issue I'm facing is I have the product connection related to Category as previously shared. On the product query I am not allowed to put a filter on the productConnection part of the query, because I have the filter in the productConnection filtering by _id. When I remove this filter I can place filter() on the productConnection part of the Category query, but then I lose the ability to filter by id
const extendedResolver = ProductTC
.getResolver('connection')
.addFilterArg({
name: 'nameRegex',
type: 'String',
description: 'Filter by product id',
query: (query, value, resolveParams) => { // eslint-disable-line
query.name = new RegExp(value, 'i');
},
});
extendedResolver.name = 'connection';
ProductTC.addResolver(extendedResolver);
I've got my custom type and extended resolver like so:
const SelectedAttributeType = InputTypeComposer.create(new GraphQLObjectType({
name: 'SelectedAttribute',
fields: () => ({
group: { type: GraphQLString },
values: { type: GraphQLList(GraphQLString) },
}),
}));
const extendedResolver = ProductTC
.getResolver('connection')
.addFilterArg({
name: 'attributeFilter',
type: new GraphQLList(SelectedAttributeType.getType()),
description: 'Filter by attribute groups',
query: (query, value, resolveParams) => { // eslint-disable-line
query.name = new RegExp(value, 'i');
},
});
extendedResolver.name = 'connection';
ProductTC.addResolver(extendedResolver);
This does not build, however, giving me:
Error: SelectedAttribute fields must be an object with field names as keys or a function which returns such an object.
Removing the function and making it an object breaks it further, giving me the
TypeError: Cannot call a class as a function error.
also you should consider a donate button. This is really cool!
if i got req.user populated from express-jwt.
Hey there, new to the project and looking for some help provided the lack of documentation. I'm migrating from a RESTful API with several endpoints. Anyone available to point me in the right direction for docs? Right now I believe I have everything setup correctly, however, I cannot seem to get the darn GraphiQL UI to show me the Root Types.
I'm using the Northwind project as an example.
maybe wrapping the resolvers would be the correct approach?
Hello guys, I've been working with a plugin associated with graphql-compose (https://github.com/graphql-compose/graphql-compose-elasticsearch). I've been using the ObjectTypeComposer from Elastic mapping for single indexes, but I'd like to be able to create a resolver that can hit multiple indexes and then use child GraphQL types per index. Has anyone done something like this? Using elasticApiFieldConfig I can wrap the entire ES API and do multi-index searches that way but then you sacrifice types as this resolver returns JSON as the type.
Hi, all.
Could you help why in my Mongoose schema property is required but it generates as optional property in graphQL schema?
const categoryScheme = new Schema(
{
name: {
type: String,
required: true,
unique: true,
maxlength: 120,
},
// ..
type Category {
_id: MongoID!
createdAt: Date
images: [String]
name: String
updatedAt: Date
}name should be with ! in the end name: String!
Hey. I am a bit new to graphql. I am using graphql-compose-mongoose and I have two mongoose models setup. Example: Owner / Pet. The owner can have multiple pets and the pet has one owner. When you setup the relationship with graphql-compose-mongoose it requires you to have subfields for the relationship. Is it possible to get just the mongo id if you don't provide any subfields? Example below:
query {
petMany {
name
owner
}
}
// vs
query {
petMany {
name
owner {
_id
}
}
}