-
Notifications
You must be signed in to change notification settings - Fork 137
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
Drop the events system #468
Conversation
Codecov Report
@@ Coverage Diff @@
## master #468 +/- ##
==========================================
- Coverage 32.32% 32.09% -0.23%
==========================================
Files 50 44 -6
Lines 3276 3103 -173
==========================================
- Hits 1059 996 -63
+ Misses 2123 2017 -106
+ Partials 94 90 -4
Continue to review full report at Codecov.
|
ea5ece4
to
b406c0f
Compare
@detiber do you mind to have a look at this please? |
19cba21
to
01c09e6
Compare
01c09e6
to
7a9229c
Compare
Signed-off-by: Gaurav Gahlot <[email protected]>
Signed-off-by: Gaurav Gahlot <[email protected]>
Signed-off-by: Gaurav Gahlot <[email protected]>
7a9229c
to
ce914db
Compare
@gauravgahlot So once this PR is merged, the 8000 bytes limit from the triggers will be solved right? |
@moadqassem After this PR is merged there will be no event triggers at all. 😄 |
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
Description
The PR removes all the code and DB changes related to the events system.
Why is this needed
Fixes: #464
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
This is a breaking change, especially for any users currently using events.
If your tool is not using tink events the migration should be smooth.
Checklist:
I have: