Review differences in the compatibility suite tests between older and new parser version

[derberg]

These files were successful in https://github.com/asyncapi/tck/ in old parser version but with latest they are wrong:

• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Correlation%20ID%20Object/valid.yaml
• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Object/valid-internal-ref-correlationId.yaml
• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Object/valid-internal-ref-header.yaml
• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Trait%20Object/valid-internal-ref-correlationId.yaml
• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Trait%20Object/valid-internal-ref-header.yaml
• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Parameter%20Object/valid-parameter-not-defined.yaml
• https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Server%20Variable%20Object/valid-variable-not-defined.yaml

Investigate what went wrong, are some bugs introduced with latest version?

[derberg]

https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Parameter%20Object/valid-parameter-not-defined.yaml
https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Server%20Variable%20Object/valid-variable-not-defined.yaml

For above examples, we throw errors, which makes sense but they are not a must required by the spec so we probably need to add some error levels (like error and warning) or simple flag that enables additional strict error handling:
#119 (comment)

[derberg]

https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Correlation%20ID%20Object/valid.yaml
https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Object/valid-internal-ref-correlationId.yaml
https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Object/valid-internal-ref-header.yaml
https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Trait%20Object/valid-internal-ref-correlationId.yaml
https://github.com/asyncapi/tck/blob/master/tests/asyncapi-2.0/Message%20Trait%20Object/valid-internal-ref-header.yaml

all above will be fixed with #138

[asyncapi-bot]

🎉 This issue has been resolved in version 0.28.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀