fix: Add support for receiving roStoryX, roItemY messages (SOFIE-2858) #87
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.
About the Contributor
This PR is posted on behald of the NRK.
Type of Contribution
This can be considered a bug fix. It adds support for a few missing MOS messages, that should have been there from the start.
This doesn't affect the consumer-side API of the library.
Current Behavior
As reported in #86 and #57, if, for example, a
<roStoryReplace>
message is received, the library will emit the error"Unsupported function"
.While these types of messages are considered deprecated_ they should still be supported.
Quote from the mos protocol documentation:
New Behavior
Library now supports the following messages:
All these messages have equivalent functionality in the
roElementAction
which is already supported, so a call to one of these will result in calls to the already existing callbacks (so no code changes are required in the consumer code).Testing Instructions
This can be tested using
Other Information
Status