[FIX] update in openAPI documentation to reach consistency with responseCode field #3766
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
Codecov Report
@@ Coverage Diff @@
## develop #3766 +/- ##
==============================================
+ Coverage 39.21% 52.65% +13.44%
Complexity 26 26
==============================================
Files 1865 1865
Lines 35275 35275
Branches 2786 2786
==============================================
+ Hits 13832 18573 +4741
+ Misses 20752 15738 -5014
- Partials 691 964 +273 |
Coduz
approved these changes
May 2, 2023
Coduz
added
Bug
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.
Analyzing the code I found that the "responseCode" device Events field possible set of values was updated in release 1.5 with the SENT value and the documentation was not consequently updated, something that I have done with this PR