Replies: 2 comments 1 reply
-
I don't think that using the "deposit" word is accurate because:
And the My choices are:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Closing as #305 has been merged. We ended up going with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As discussed in #204, I find the
grossDepositAmount
param name rather verbose. It's a good fit for the create functions but there's something bugging me about there being three words in the name. In addition, there's a question of marketing at play here - we don't want to give an indication that fees are charged by default when in fact they aren't.Suggested alternatives ordered by how much I like them:
totalAmount
depositAmount
lockupAmount
grossAmount
amount
None is great, and I can come up with an explanation for why
grossDepositAmount
is a better fit than each of the above. But we gotta start somewhere - WDYT?For me,
depositAmount
is the leading candidate, since I expect many V2 streams to be fee-less. For fee-less streams, the "gross deposit amount" is the same as the struct "deposit amount". Conversely, the fees should be small anyway, so it's fine to call the function name "deposit amount" just like the struct because they will have approximately the same value.totalAmount
is my second favorite candidate, because it communicates the fact that there is something more than just the deposit amount in this function param (i.e. the amount that gets stored in the struct as.amounts.deposit
).Alternatively, we could consider renaming the
amounts.deposit
in the struct to something else .. though that would also mean renaminggetDepositAmount
.Beta Was this translation helpful? Give feedback.
All reactions