Custom endpoint sends back localized fields

nh02.2 years ago

3

...
endpoint: [{
...
handler: async (req, res) => {
        const { payload, query } = req;

        const teamMembers = {
          docs: await payload.collections['team-members'].Model.find()
            .sort({
              order: -1,
              lastNameWithoutPrefix: 1,
            })
            .limit(parseInt(query.limit as string))
            .skip(
              (parseInt(query.page as string) - 1) *
                parseInt(query.limit as string),
            ),
        };
        return res.status(200).send(teamMembers);
     },
...
}]

localizedField: {nl: 'string value'}

localizedField: 'string value'

• 

  notchr2 years ago

  @934107997687402547

  what if you specify the

  locale

  property on the find request

  
  
  

  Does that then deliver the string value?

• 

  jmikrut

  2 years ago

  so, because you're using the Mongoose model directly (and not the Payload

  find

  operation) Mongoose is just sending back the raw document itself (including all locales). Payload's operations are responsible for the localization "flattening", not Mongoose. If I were you, I'd try to leverage the Payload local api instead of the raw Mongoose model. But if you can't do that, you could always run the Payload

  afterRead

  field hooks manually against the documents that are returned from Mongoose

  
  
  

  here is where we "flatten" locales within the Payload core itself:

  
  
  https://github.com/payloadcms/payload/blob/master/src/collections/operations/find.ts#L192
  
  

  notice how we pass in the raw Mongoose docs?

  
  
  

  once they come back out, they will have locales "flattened". The

  locale

  is set on the

  req

  and then the

  afterRead

  hook is what looks at that, and then flattens the locales into the locale you ask for via the query param

  ?locale=myLocale
• 

  nh02.2 years ago

  Alright it works! Thank you 🙆‍♂️

  @364124941832159242