patternProperties not being rendered on studio

[menego]

Hello everybody. I do not know if this is a bug or an enhancement but in my current spec I strongly rely on patternProperties and I have noticed that the current version of the studio does not render them correctly.
e.g.:

asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
components:
  schemas:
    Shadow:
      type: object
      patternProperties:
          "^service:camera:[0-9]{1,}$":
            $ref: "#/components/schemas/Camera"
    Camera:
      type: object
      properties:
        id:
          type: string
          format: uuid

is rendered as a generic Any instead of showing the underlying object spec

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[menego]

Closed related discussion in Q&A: #1222

[menego]

ADD:
Interesting behavior I just discovered, patternProperties works correctly if there is at least one property in the object but according to the official JSON spec as well as their examples this should not be the case.

asyncapi: 3.0.0
info:
  title: Account Service
  version: 1.0.0
components:
  schemas:
    Shadow:
      type: object
      properties:
        abba:
            type: string
      patternProperties:
        "^service:camera:[0-9]{1,}$":
            $ref: "#/components/schemas/Camera"
    Camera:
      type: object
      properties:
        id:
          type: string
          format: uuid

https://studio.asyncapi.com/?share=634cd1e7-9975-447f-a449-3535debe7e2f

[theAnuragMishra]

Sounds like a parser bug.

Edit: I checked and it's definitely not a parser bug. So it's a frontend bug in the studio but I can't really locate the source.

[theAnuragMishra]

After some (hours of) navigating between packages, I hv found that the bug is in asyncapi-react package. I have created and linked an issue. Let's move the further discussion about this bug there.