-
Notifications
You must be signed in to change notification settings - Fork 83
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
feat: Expect V2 Event DTO from triggers. #616
feat: Expect V2 Event DTO from triggers. #616
Conversation
ddfe917
to
4e36144
Compare
Putting this on hold as the DTO that will be received from the MessageBus is changing from |
b8d681f
to
a57b559
Compare
Codecov Report
@@ Coverage Diff @@
## master #616 +/- ##
==========================================
+ Coverage 60.98% 62.24% +1.26%
==========================================
Files 31 31
Lines 1830 1907 +77
==========================================
+ Hits 1116 1187 +71
+ Misses 640 639 -1
- Partials 74 81 +7
Continue to review full report at Codecov.
|
8c202e8
to
6a64ff4
Compare
6f4c8a6
to
ce7c848
Compare
Triggers expect a V2 AddEventRequest DTO Appropriate pipeline functions now expect a V2 Event DTO. V1 Event model temporarily supported by converting V1 Event to a V2 Event DTO. closes #595 Signed-off-by: lenny <[email protected]>
ce7c848
to
578b4c2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall looks ok, i saw lots of temporary v1 stuffs and some error checks i think we should put in IMO
Signed-off-by: lenny <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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?
Triggers and some pipeline function expect a V1 Event model
Issue Number: #595
What is the new behavior?
Triggers and appropriate pipeline functions now expect a V2 Event DTO.
V1 Event model temporarily supported by converting V1 Event to a V2 Event DTO.
Does this PR introduce a breaking change?
Are there any new imports or modules? If so, what are they used for and why?
no
Are there any specific instructions or things that should be known prior to reviewing?
Other information