Changes in AMF 5.2.5
What's Changed
- Add typing for grpc configuration by @pope1838 in #1717
- (fix): properties with same semantics but different sub tree weren't being merged by @tomsfernandez in #1718
- W-12438860: syntax recovery by @nschejtman in #1725
- W-12385375: refactor getDeclaringUnit logic to improve performance by @nschejtman in #1726
- W-11351848: added discrminator value validation candidate collector by @nschejtman in #1727
- W-12361132 (fix): removed ast tampering in and, or and xone parsers by @tomsfernandez in #1729
- W-12521486: fixed wrong type expression parsing by @tomsfernandez in #1728
- W-11680259: avoid throwing remote context error in canParse method by @arielmirra in #1730
- update typings with JSONLD features by @arielmirra in #1739
Important validation - New RAML type validation
When a raml type has the value type: []
we now validate it with the message [] is not a valid type
.
For example in the following API:
/test:
post:
body:
application/json:
properties:
products: []
The type of products
is not valid, and the validation [] is not a valid type
will show up.
Full Changelog: 5.2.4...5.2.5