Mongo ObjectID && keyHere option

Question

Mongo ObjectID && keyHere option

astralmedia opened this issue 4 years ago · comments

Hey! Thanks for the awesome work.

I am trying to integrate this, but cant seem to get it working. I've gone back thru the docs many times t be sure it's setup properly...

I am wondering if maybe it has to do with the ObjectID type of _ID that mongo uses. Would keyHere: "_id" map to the _id: ObjectID("j89f2nj8iofjf") or is it expecting a string/int only?

Scott Hedstrom · Answer 1 · Tue Apr 14 2020 03:34:08 GMT+0800 (China Standard Time)

So, after a bit more testing, I am able to get it working if I duplicate the mongo _id to be a normal key:string like id:891ue399

tho this will end up becoming extremely redundant...are you familiar with a way to use the mongo ObjectID instead as the keyThere?

Marshall Thompson · Answer 2 · Tue Apr 14 2020 04:42:15 GMT+0800 (China Standard Time)

I'll publish something, today, that will make this much easier for you.

Scott Hedstrom · Answer 3 · Tue Apr 14 2020 05:05:58 GMT+0800 (China Standard Time)

Thanks so much :)

Really loving this library.

Quick question, how would you organize your populates & namedQueries in a growing app? I am thinking about having a whatever.relationships.js file next to the whatever.services.js, but I want to be sure...Or am I overthinking this and you really only need one file for all of them?

Marshall Thompson · Answer 4 · Tue Apr 14 2020 06:09:08 GMT+0800 (China Standard Time)

I put populates at the top of the hook file. I don’t mind the 20 ish lines at the top of the file. I usually keep my hooks in their own files, so having the relationships in the hooks file doesn’t bug me. I actually started out by keeping them separate, but later moved then all in and it was a simpler process for me

…

Sent from my iPhone

On Apr 13, 2020, at 3:06 PM, Scott Hedstrom ***@***.***> wrote: Thanks so much :) Really loving this library. Quick question, how would you organize your populates & namedQueries in a growing app? I am thinking about having a whatever.relationships.js file next to the whatever.services.js, but I want to be sure...Or am I overthinking this and you really only need one file for all of them? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Marshall Thompson · Answer 5 · Tue Apr 14 2020 08:30:42 GMT+0800 (China Standard Time)

Ok. I just published something that will simplify this process: https://github.com/feathers-plus/validate-joi-mongodb

Marshall Thompson · Answer 6 · Tue Apr 14 2020 08:32:09 GMT+0800 (China Standard Time)

Specifically, check out the objectIdsInQuery utility in the above link.

Scott Hedstrom · Answer 7 · Tue Apr 14 2020 09:13:10 GMT+0800 (China Standard Time)

Thanks @marshallswain I will take a look. You are a dev angel :)

Scott Hedstrom · Answer 8 · Tue Apr 14 2020 12:19:35 GMT+0800 (China Standard Time)

So, curious how this works actually...I am passing what turns into an ObjectID to a route param:

/endpoint/tokenval_which_is_also_objectID_string

I followed the installation instructions, and after reconfiguring to use the _id as the keyThere, the result stopped coming back.

Will I need to make this into a param that is passed?

Scott Hedstrom · Answer 9 · Wed Apr 15 2020 04:28:43 GMT+0800 (China Standard Time)

Tried digging in deeper here, but was unable to figure it out.

Im working on a custom endpoint that overrides the create method, and gets an entry, which has the foreign relationship objects referenced, but nothing is in the query{} at this point when the hook calls.

Should I go thru the returned object and convert it's string to ObjectID in a custom hook for this u think? I tried converting it to an ObjectID reference in the DB, may be smarter to just store the objectids yea?

thanks again, sorry if this is all over the place lol

Marshall Thompson · Answer 10 · Thu Apr 30 2020 09:54:58 GMT+0800 (China Standard Time)

@astralmedia Are you wanting to use this in a service.get request? I think it needs to convert context.id to a full ObjectId, if that's the case. The objectId utility in that other project can be used standalone. Sorry this is late. Were you able to figure anything out?