Document messaging.operation.name for azure messaging systems
#942
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 tasks
pyohannes
reviewed
Apr 22, 2024
trask
reviewed
Apr 22, 2024
|
|
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
lmolkova
force-pushed
the
azure-messaging-list-all-and-operation-type
branch
from
01ae151
to
6b4a51f
Compare
lmolkova
force-pushed
the
azure-messaging-list-all-and-operation-type
branch
from
6b4a51f
to
cbf3f20
Compare
lmolkova
changed the title
messaging.operation.names and clarity list of applicable attributesmessaging.operation.name for azure messaging systems
joaopgrassi
approved these changes
Jun 17, 2024
pyohannes
approved these changes
Jun 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #926
Changes
Also addresses the Azure-messaging specific portion on #869
Merge requirement checklist
[chore]schema-next.yaml updated with changes to existing conventions.