Skip to content

feat(eventstream-serde-universal): omit unknown event type #1325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 8, 2020

Conversation

AllanZhengYP
Copy link
Contributor

When an event returns from response event stream is not defined in the model. The deserialize will parse it as {$unknown: {Event: Payload}}. In this case, the downstream event stream should omit this event, instead of emitting an event with name $unknown.

This PR implements the change and unit test.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@codecov-commenter
Copy link

Codecov Report

Merging #1325 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1325   +/-   ##
=======================================
  Coverage   89.34%   89.35%           
=======================================
  Files         152      152           
  Lines        3145     3147    +2     
  Branches      579      580    +1     
=======================================
+ Hits         2810     2812    +2     
  Misses        335      335           
Impacted Files Coverage Δ
...tream-serde-universal/src/getUnmarshalledStream.ts 75.00% <100.00%> (+1.92%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d018293...fd2c9df. Read the comment docs.

@AllanZhengYP AllanZhengYP merged commit 54d2429 into master Jul 8, 2020
@trivikr trivikr deleted the handle-undefined-events branch July 8, 2020 23:04
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants