-
Notifications
You must be signed in to change notification settings - Fork 117
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
refactor: sources to v2 batch3 #4087
base: develop
Are you sure you want to change the base?
Conversation
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4087 +/- ##
===========================================
+ Coverage 91.13% 91.14% +0.01%
===========================================
Files 629 629
Lines 32837 32875 +38
Branches 7791 7791
===========================================
+ Hits 29925 29963 +38
Misses 2696 2696
Partials 216 216 ☔ View full report in Codecov by Sentry. |
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
|
What are the changes introduced in this PR?
Modified below sources to accept and process v2 spec.
What is the related Linear task?
Resolves INT-3256
Please explain the objectives of your changes below
This is one set of sources that are migrated to v2 specification completely. This is part of the
Webhook Sources Improvements
project.Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?
All the above sources process v2 specification instead of vo and v1.
Any new dependencies introduced with this change?
No
Any new generic utility introduced or modified. Please explain the changes.
message
class utilised by all sources is replicated and placed in sources folder. This will be the norm for all sources with this projectAny technical or performance related pointers to consider with the change?
No
@coderabbitai review
Developer checklist
My code follows the style guidelines of this project
No breaking changes are being introduced.
All related docs linked with the PR?
All changes manually tested?
Any documentation changes needed with this change?
Is the PR limited to 10 file changes?
Is the PR limited to one linear task?
Are relevant unit and component test-cases added in new readability format?
Reviewer checklist
Is the type of change in the PR title appropriate as per the changes?
Verified that there are no credentials or confidential data exposed with the changes.