How do you query z.array() fields (e.g. tags) in the latest nuxt-content module (v3.alpha.8)

[humblemodulo]

In the previous version of nuxt-content (v2) I would simply query tags like so:

  .where({ tags: { $contains: tagSlug } })

However there is no contains in v3, and the logic for IN seems to require the reverse operation. I've tried LIKE and that doesn't work either.

Definitely need to know the best way to find values in z.array() field types.

As it stands, I'm forced to retrieve all, then run JS .filter() on the results. Quite inefficient.

[aatrooox]

I have a similar need for filtering tags

like this:

let query = queryCollection('content').where('tags', 'LIKE', `%${tag}%`)

if filter multiple：

let query = queryCollection('content')
  if (filter_tags.length) {
    filter_tags.forEach(tag => {
      query = query.where('tags', 'LIKE', `%${tag}%`)
    })
  }

query.order('date', 'DESC').all()

Because I found that the 'tags' field in the SQLite database is merely of type Text.

so, it can only be filtered using LIKE...

if you have a better way, please tell me 😀

[matteioo]

While the solution @aatrooox is probably already the best you can get regarding the runtime (correct me if I'm wrong) but I thought I'd share my solution with you, since the solution above works for logical AND concatenation of the tags but wouldn't work when wanting to concatenate the tags using logical OR.

Luckily, there are andWhere as well as orWhere which allow us to concatenate additional statements as the name implies logically AND or OR.

As an example, with the following code you can filter the content collection which match all the provided tags.

const fetchContent = async () => {
  const query = queryCollection('content')
  if (filter_tags.length) {
    query.andWhere(q => {
      filter_tags.forEach(tag => q.where('tags', 'LIKE', `%${tag}%`))
      return q;
    })
  }
  return await query.all()
}

By using either andWhere or orWhere you can choose which logical concatenation of the tag statements you would like to use. And at least I myself would state that the code is readable for outsiders, as it is near to SQL syntax. Furthermore, it is easy to adapt and extend with more nested statements (both AND and OR) to fine-tune the query.

Hope this helps anyone in the future who visits this thread 👍