feat(sdk): Use ResponseContentType in MessageBus #644
Merged
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
Use edgexcontext.ResponseContentType in messagebus trigger output if set. If not set infer JSON / CBOR as in MQTT trigger. Signed-off-by: Alex Ullrich <alexullrich@technotects.com>
Codecov Report
@@ Coverage Diff @@
## master #644 +/- ##
==========================================
+ Coverage 60.83% 60.98% +0.14%
==========================================
Files 31 31
Lines 1823 1830 +7
==========================================
+ Hits 1109 1116 +7
Misses 640 640
Partials 74 74
Continue to review full report at Codecov.
|
|
recheck |
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.
Use edgexcontext.ResponseContentType in messagebus trigger output if
set. If not set infer JSON / CBOR as in MQTT trigger.
Signed-off-by: Alex Ullrich alexullrich@technotects.com
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number:
#540
What is the new behavior?
Does this PR introduce a breaking change?
Are there any new imports or modules? If so, what are they used for and why?
Are there any specific instructions or things that should be known prior to reviewing?
Other information