Update errormessage for unsupported device identifieres#261
Merged
jlurien merged 7 commits intocamaraproject:mainfrom Nov 19, 2024
Merged
Conversation
jlurien
reviewed
Sep 27, 2024
Collaborator
jlurien
left a comment
There was a problem hiding this comment.
For any change in the specs in the main branch we have to set versions to wip again
Collaborator
We have to decide if changes are worthy for a new release. I would wait until we have something really relevant, and in that case update all small things as well |
Contributor
Author
jlurien
previously approved these changes
Oct 21, 2024
Collaborator
akoshunyadi
reviewed
Nov 19, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Fixing a typo / mistake in the error for
GENERIC_422_UNSUPPORTED_DEVICE_IDENTIFIERSWhich issue(s) this PR fixes:
Fixes #260