-
Notifications
You must be signed in to change notification settings - Fork 50
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: remove broker #1166
refactor: remove broker #1166
Conversation
ad17297
to
081789a
Compare
test: deploy contracts in fork tests
Yes I was not expecting it to reduce 800 lines. Clearly a good call to remove the broker fee.
OK. Sounds good to me. I'd suggest to take the opinion of Razvan and Mircea on it though since it only affects the app. |
cc @sablier-labs/frontend |
1a5eeb2
to
8236b66
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.
Great work on the PR @andreivladbrg. I have pushed a small commit (d62a8d4) just some natspec fixes and moved Base_Test.setUp()
under TODO
tag to signal it clearly that it needs to be removed later.
If all looks good, you can go ahead and merge it.
Re CreateEventCommon
, can we do it in another PR and as a separate issue for easier review?
I have also not reviewed benchmarks
dir since it will be removed in the future (#1170). I hope thats OK.
sounds good
that's ok, just keep in mind when you work on the new repo that there were made some changes in this branch btw, pushed a commit to crease the coverage, don't know how we have missed it until now |
Yes we both will be co-authors of those changes. Also, in the future PR, in case it requires making changes to the benchmark code, then lets just remove it (#1170).
Good catch. |
Closes #1157
I also decided to rename the
totalAmount
parameter todepositAmount
, as there was no other amount in thecreate
function. I’m also considering removing theCreateEventCommon
struct, as I believe we will no longer encounter the "Stack too deep" error, the only problem is that it will cause more changes to the app. @smol-ninja wdyt?I'm surprised by how much this change reduces the code! This would be advantageous for integrators as well.