Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add messages field in the Operation Object #870

Conversation

magicmatatjahu
Copy link
Member

@magicmatatjahu magicmatatjahu commented Nov 9, 2022


title: "add messages field in the Operation Object"


Related issue(s):
#618
#858 - another solution to fix "reusability" of messages in channels


Change is suggested by #618 (comment) and #618 (comment)

messages (Messages Object) - A map of the messages that will be processed by this operation at any time during the runtime of the application. The map should contain a subset of messages that are defined in the corresponding channel. If the field is omitted, the operation performs an action on every message defined in the corresponding channel.

spec/asyncapi.md Outdated Show resolved Hide resolved
@fmvilas
Copy link
Member

fmvilas commented Nov 14, 2022

Let's hold this until we're clear with #847.

Co-authored-by: Fran Méndez <fmvilas@gmail.com>
@sonarcloud
Copy link

sonarcloud bot commented Nov 21, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@magicmatatjahu
Copy link
Member Author

Will be supported in #847

@magicmatatjahu magicmatatjahu deleted the next-major/operation-messages branch February 2, 2023 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants