load error java.lang.Boolean cannot be cast to io.swagger.v3.oas.models.media.Schema.

[MishaTyupa]

Description
One example of when it is not working and we are getting a casting error when we try to run specmatic test with swagger YAML file is when we have the following YAML(that's a part of swagger YAML file)

    SomeService:
      type: object
      properties:
        name:
          type: string
          nullable: true
        host:
          type: string
          nullable: true
        hostName:
          type: string
          nullable: true
      **additionalProperties: false**

It cannot be parsed and I'm getting a java error: load error java.lang.Boolean cannot be cast to io.swagger.v3.oas.models.media.Schema. If I remove additionalProperties: false, then it works. So definitely something that can be improved to cast such YAML also. There are more examples when it failed to cast additionalProperties: {} etc.

Steps to reproduce

1. run specmatic test using swagger open API (3.0.1 version)

Expected result
Tests are executed

[MishaTyupa]

is there any progress?

[jaydeepk]

Thanks for reporting this issue @MishaTyupa .
We will get back to you once we have a fix ready.

[TheRubble]

Any updates on this as it's currently stopping our migration from PACT. Happy to pitch in if someone could provide some guidance etc.

[harikrishnan83]

@MishaTyupa @TheRubble Thank you for your patience. We just merge the fix for this issue. And this will be part of our upcoming release. We will keep you posted on this thread.
cc @jaydeepk @joelrosario

[TheRubble]

Thanks ever so much, do you have any idea on when the next release is?

[joelrosario]

@TheRubble We've just released 0.73.0.

[jaydeepk]

The fix for this has been released in v 0.73.0.
Please feel free. to reopen if the issue persists.

[MishaTyupa]

The issue is not present anymore. Thanks, guys. However, there is one room for improvement that I found would be useful to integrate into specmatic. Here is an example of how specmatic cannot parse a value from {version} variable. /api/v*{version}*/Banner/active and how it works: /api/v*1*/Banner/active Should I create a new ticket for that? Thanks for your job, guys. пт, 4 авг. 2023 г. в 13:00, Jaydeep Kulkarni ***@***.***>:

…

Closed #646 <#646> as completed. — Reply to this email directly, view it on GitHub <#646 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTAW3BLXTC2IAU5YX36JODXTTB2BANCNFSM6AAAAAAXMCP7TY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[harikrishnan83]

@MishaTyupa Thanks. Yes, please do create another ticket to track the issue where Specmatic is not able to parse {version} variable when it is a substring of a path part.

[MishaTyupa]

the new issue is submitted. #693 сб, 5 авг. 2023 г. в 11:47, HariKrishnan ***@***.***>:

…

@MishaTyupa <https://github.com/MishaTyupa> Thanks. Yes, please do create another ticket to track the issue where Specmatic is not able to parse {version} variable when it is a substring of a path part. — Reply to this email directly, view it on GitHub <#646 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTAW3H33T6MX25LTNL52UDXTYCC3ANCNFSM6AAAAAAXMCP7TY> . You are receiving this because you were mentioned.Message ID: ***@***.***>