Update the ID values for the Communication API examples #50
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
|
Ich vermute, das wird durch PR 47 sowieso weitgehend erledigt, außer bei den Beispiele, die nicht vollständig sind |
Update Validate Examples Action
Update the checkout, setup-node and setup-java actions to the latest major version
florianschoffke
requested changes
Aug 19, 2024
florianschoffke
approved these changes
Aug 19, 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.
The API examples for the Communication calls had odd IDs like "12345" or "123450". This pull request changes that and replaces them with UUIDs.
It is, however, important to remember that the IDs are just strings.