filter-in on tags includes operations that don't have a tag

[michael-wolfenden]

Describe the bug

filter-in on tags includes operations that don't have a tag

To Reproduce
Steps to reproduce the behavior:

1. Given this redocly.yaml file

decorators:
  remove-unused-components: on
  filter-in:
    property: tags
    value: [cats]
    matchStrategy: all

2. And this OpenAPI file(s) spec.yml

NOTE; /dogs doesn't contain a tags property

openapi: "3.0.0"
info:
  version: 1.0.0
  title: Swagger Petstore
paths:
  /cats:
    get:
      tags:
        - cats
      responses:
        200:
          description: A list of cats
          content:
            text/plain:
              schema:
                type: string
  /dogs:
    get:
      responses:
        200:
          description: A list of dogs
          content:
            text/plain:
              schema:
                type: string

3. Run this command with these arguments... redocly bundle .\spec.yaml --config .\redocly.yaml --output .\output.yml
4. output.yml contains both operations

openapi: 3.0.0
info:
  version: 1.0.0
  title: Swagger Petstore
paths:
  /cats:
    get:
      tags:
        - cats
      responses:
        '200':
          description: A list of cats
          content:
            text/plain:
              schema:
                type: string
  /dogs:
    get:
      responses:
        '200':
          description: A list of dogs
          content:
            text/plain:
              schema:
                type: string

Expected behavior

I would have expected the output to only contain the /cats operation.

NOTE; filter-in works correctly if

• /dogs has a tag

  /dogs:
    get:
      tags:
        - dogs

• /dogs has an empty tags property

  /dogs:
    get:
      tags: []

Redocly Version(s)

redocly --version
1.13.0

Node.js Version(s)

node -v
v20.11.0

OS, environment

Windows

[emaas]

We are running into the same issue.

Looking at the code, it looks like this behavior is on purpose:
should include path without x-audience property
I do however agree that this is unexpected behavior.
And we are also running into this issue.

Perhaps a new match strategy can be added. Something like any_excluding_empty, and all_excluding_empty?

Another approach would be to add a decorator called "filter_out_non_existing" that would have the responsibility of filtering out items not containing a certain property.