Documentation of MessageObject "deprecated" property about spec-json-schemas HOT 28 CLOSED

Welcome to AsyncAPI. Thanks a lot for reporting your first issue.

Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

from spec-json-schemas.

Good catch @c-pius, can see the parser does not have the property as well. Tagging @fmvilas to get his perspective, think this is something that was added early on.

from spec-json-schemas.

I can see that messageTrait andchannelItem also contains a deprecated property which are not present in the tools.
https://github.com/asyncapi/asyncapi/blob/5ad3a971c82b33717fdec4c8d78173294ae253ff/versions/2.0.0/schema.json#L909
https://github.com/asyncapi/asyncapi/blob/5ad3a971c82b33717fdec4c8d78173294ae253ff/versions/2.0.0/schema.json#L501

from spec-json-schemas.

Related issue about introducing deprecation/sunset property for the channel - asyncapi/spec#305

from spec-json-schemas.

I don't think the deprecated flag is supported on a Message or a Channel level. At least I know about Channel -> asyncapi/html-template#81 (comment) but don't remember where from 😅

It might be just a bug in the schema. Remember that schema != spec md file

But yeah, @fmvilas should confirm

from spec-json-schemas.

Yeah, I think that's a bug. Always follow the Markdown version of the spec. However, if you think that it still makes sense to have a deprecated property at MessageObject level, then let's open an issue to propose it.

from spec-json-schemas.

Alright, thanks for the info. I also just encountered the deprecated property by chance. As of now our use case doesn't require a deprecated property on message level. But I could imagine this in the future (maybe even with some more information like successor message, sunset date, etc). If so, I would think about an own extension or proposing something for the MessageObject.

For now you can close this issue from my side.

from spec-json-schemas.

Yes, there's a feature request for this (although at channel level): asyncapi/spec#305. Leaving this open because it needs to be fixed. Thanks!

from spec-json-schemas.

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

from spec-json-schemas.

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.

from spec-json-schemas.

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

from spec-json-schemas.

/help

from spec-json-schemas.

Hello, @derberg! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

from spec-json-schemas.

Hey @asyncapi-bot, something is wrong with your command please use /help for help.

from spec-json-schemas.

Hello, @asyncapi-bot! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

from spec-json-schemas.

Hey @asyncapi-bot, something is wrong with your command please use /help for help.

from spec-json-schemas.

Hello, @asyncapi-bot! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

from spec-json-schemas.

Hey @asyncapi-bot, something is wrong with your command please use /help for help.

from spec-json-schemas.

Hello, @asyncapi-bot! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

from spec-json-schemas.

Hey @asyncapi-bot, something is wrong with your command please use /help for help.

from spec-json-schemas.

Hello, @asyncapi-bot! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

from spec-json-schemas.

@KhudaDad414 have a look, I luckily made it stop 😆

from spec-json-schemas.

Also, when fixing can you also improve below message. My bot complains it is not much positive, probably because of wrong

from spec-json-schemas.

/help

from spec-json-schemas.

Hello, @derberg! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

from spec-json-schemas.

/gfi docs

from spec-json-schemas.

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

from spec-json-schemas.

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

from spec-json-schemas.