I'm happy to submit a PR with a possible implementation
i am starting to get a hang of this code now.. it is a little complex..
User.find({
'$or':[
{firstname:new RegExp(searchText,'i')},
{lastname:new RegExp(searchText,'i')},
{email:new RegExp(searchText,'i')}
]});
})
Hello @nodkz. I'm still interested in building the knex plugin. I'm also trying to learn how to use the API to get a better understanding ( so I can write the knex plugin! ). I've noticed in https://github.com/nodkz/graphql-compose/tree/master/docs/04-api-reference that there are examples like:
GQC.rootQuery().addFields({
city: CityTC.get('$findOne'),
cityConnection: CityTC.get('$connection'),
currentTime: {
type: 'Date',
resolve: () => Date.now(),
},
// ...
});
GQC.rootMutation().addFields({
createCity: CityTC.get('$createOne'),
updateCity: CityTC.get('$updateById'),
// ...
});
But how are those
get calls resolved? Where is e.g. $createOne defined? Is this a mongoose method?
is this room still active?
Last message i see in Jan 22.
@cellis just feel free to ask, i will be more online from now and forward :wink:
Hi, everyone
I need a help.
So, I have a Shema
const UserSchema = new Schema({
name: String,
gender: {
type: String,
enum: ['male', 'female', 'ladyboy'],
},
city: String
},
{
collection: 'users'
});
const User = mongoose.model('User', UserSchema);
const UserTC = composeWithRelay(composeWithMongoose(User));
...I have add new field
UserTC.addFields({
foo: {
type: GraphQLString,
projection: { test: true, gender: true },
resolve: (source) => (`${source.test} ${source.gender}`)
},
})And I would like add another field depended from foo field
UserTC.addFields({
bar: {
type: GraphQLString,
projection: { foo: true },
resolve: (source) => (`${source.foo} is awesome`) // but source.foo is undefined
},
})But source.foo is undefined. What should I do for fix it ?
Thanks
try:
UserTC.addFields({
foo: {
type: GraphQLString,
projection: { test: true, gender: true },
resolve: (source) => (`${source.test} ${source.gender}`)
},
bar: {
type: GraphQLString,
projection: { foo: true },
resolve: (source) => (`${source.foo} is awesome`) // but source.foo is undefined
},
})
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.