[FEATURE] Mark deprecated properties with @Deprecated

[maltesmann]

Why do we need this improvement?

Changes in the event-model between software components implemented by different teams sometimes require to be non-breaking. Therefore to be removed properties are not removed directly but marked with deprecated: true in the specification.

How will this change help?

For the developer only working with the generated code it would be much easier to directly see the deprecation in the IDE instead of having to look out for deprecations in the specification.

Screenshots

No response

How could it be implemented/designed?

Add the @Deprecated annotation to getters and setters in generated model classes where deprecated: true

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

[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.

[asyncapi-bot]

🎉 This issue has been resolved in version 1.6.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀