Problem with `mode=tags` when endpoints have multiple tags

[ethanmdavidson]

I have a spec that uses multiple tags, e.g.

...
  /api/example/foo:
    post:
      operationId: createFooExample
      tags:
        - exampleService
        - foo
...

When I run this tool (openapi-to-k6 clients/bundled.yml clients/k6 --mode=tags --include-sample-script --verbose) it generates references to non-existent files.

k6-script.sample.ts:

...
import { ExampleServiceClient } from "./example-service.ts"
import { FooClient } from "./foo.ts"
...

example-service.ts has been generated and does exist, but foo.ts does not exist.

[DefCon-007]

Hi @ethanmdavidson

We currently have some end-to-end tests in place that handle requests with multiple tags, and they appear to be working as expected. For example, you can refer to this schema - https://github.com/grafana/openapi-to-k6/blob/main/tests/e2e/schema.json#L209
To help us investigate further, could you please share a sample schema where the issue is reproducible? Additionally, let us know which version of the OpenAPI-to-k6 tool you're using.