"Any" predicate with a field path returns 400 error if that field is both in a tab and empty in all documents

Developing with Prismic
,
1

I'm working on an article filter right now. Each article has a group field that contains a content relationship to the "Categories" custom type. I've set up the query to filter by Categories like so:

const newsArticles = await $prismic.api.query(
      [
        $prismic.predicates.any('my.news_articles.categories.category', [
          'document-id-here',
        ]),
      ],
    )

(Note: "document-id-here" is just a placeholder. I am testing this with real IDs)

If at least one of my news_articles documents has content in the "Categories" group field, the query works. However, if none of the news_articles documents have any content in the "Categories" group field, the query fails with the following error and breaks the site:

Unexpected status code [400] on URL https://example.cdn.prismic.io/api/v2/documents...

In the Network tab, the error reads:

[function any(..)] unexpected field 'my.news_articles.categories.category' on line:1 col:7 in query '[[any(my.news_articles.categories.category, ["document-id-here"])]]'\n[[any(my.news_articles.categories.category, ["document-id-here"])]]\n ^\n

After doing some digging, I found this issue only occurred if the empty field was in a tab other than Main. I was able to reproduce the error with multiple field types ONLY if they were in a different tab than Main. Prismic handled the same empty field types in the Main tab without error.

2

Hi Laura,

Welcome to the community!

This is the normal behaviour for the API to return 400 errors in this case when there are no linked documents. I agree this could be improved and show no response instead.

The strange thing is that you should see this behaviour regardless of the tab, because the tabs are only for organisation and don't effect the API response.

Thanks.

4

Okay, good to know that's normal. Just wanted to make sure I wasn't missing something. Thank you!

1 Like
6

Hi @Phil Ive just come across this issue as well. Is there any news on this query returning an empty response, this would be expected than throwing an error?

We have products that have categories assigned and show these categories on each product page currently it throws a 400 when we expect it to return empty or zero.

const products = await $prismic.api.query(
        $prismic.predicates.at(
          "my.product.categories.category",
          category.id
        ),
        {
          orderings: "[my.product.pageTitle]",
        }
      );
8

Hi @jack ,

There has been no movement on this, but we have begun a discussion about error messaging. If any changes, I'll update you here. For now though, you can assume nothing has changed and won't be changing for the foreseeable future.

Thanks.