3

Brand new to these technologies and am pretty pumped by what i see so far, i am having a rough time finding an example of something i am stuck on. The docs for react-admin suggest my schema for say Posts follows the allPosts and _allPostsMeta.. The allPosts part works no problem but naturally react-admin chokes to death on the _allPostsMeta because i am not sure how that fits into things.. Examples mostly just show what your schema should look like but don't go any further than that.. Is there a demo server app setup like this anywhere that one could look at? I have my resolvers setup using join monster presently and that all makes decent sense to me, so i guess my question is, could anyone tell me, or point me to what my resolver should look like to satisfy that _allPostsMeta query that returns ListMetadata.. i looked into a few things like resolver chaining thinking maybe i am supposed to just return the length of the Post[] from allPosts but maybe that is overcomplicating things.. Any help or explanations would be greatly appreciated...

Thanks

Greg Belyea
  • 858
  • 1
  • 5
  • 15

2 Answers2

0

appreciate this is an old question and you've probably moved on but thought I'd put a response here as I hit a similar situation myself whilst trying to implement a React-Admin front-end with an Apollo-Server-Express GraphQL back-end.

Based on the React Admin example of ra-data-graphql-simple (https://github.com/marmelab/react-admin/tree/master/packages/ra-data-graphql-simple)

My resolver ended up looking as follows:

Query: {
    _allPostsMeta: (parent, args, { db }, info) => db.post.findAndCountAll()
}

Note findAndCountAll() not findAll() as I've seen in other examples. This was enough to get React Admin pagination working for me so far. The lack of documentation / examples for all of this does make me somewhat dubious that this software is not the way to go or has been surpassed by something else.

Chris Pook
  • 51
  • 2
  • Hey Chris.... it took a while, but I have gotten it up and working the way I desired... the guys at marmelab have improved the documentation a lot and they do actually respond when you find bugs or what looks like bugs... I’m pretty happy with what I have been able to kick out for admin with their toolset in the little time I have been given to actually focus on admin... it’s great that you answered tho because I had forgot I asked this one, I usually go back and answer when I figure it out in case that helps someone else but I clearly missed this one!!! Cheers – Greg Belyea Nov 18 '19 at 17:37
0

this is what I used with a Mongoose Model in the backend

async _allPostsMeta() {
  try {
    const countAll = await Post.countDocuments();
    return {
      count: countAll,
    };
  } catch (error) {
    throw new Error(err);
  }
},

So the full resolvers looks like this

Query: {
async Post(_, { id }) {
  return await Post.findById(id);
},

async allPosts() {
  try {
    const posts = await Post.find();
    return posts;
  } catch (err) {
    throw new Error(err);
  }
},

//query for _allPostMeta
async _allPostsMeta() {
  try {
    const countAll = await Post.countDocuments();
    return {
      count: countAll,
    };
  } catch (error) {
    throw new Error(err);
  }
},

},

Zovitch
  • 33
  • 5