Closed lokka30 closed 1 year ago
Why?
Not opposed to these, but is it a large enough concern to bother? I do prefer Google's style of lowercasing subsequent letters in abbreviations. Is that specifically an inconsistency across the project?
@MrIvanPlays and @Jikoo:
transactionAmount
->amount
Prefixing amount
with transaction
whilst it is already clearly inside a transaction namespace (the EconomyTransaction
class) is verbose and pointless.
economyTransactionType
->type
Identical reasoning to the above, though this is even more verbose than the transaction amount name.
currencyID
->currencyId
As Jikoo mentioned - inconsistency. Lowercase the 'd'.
What you're doing here is creating an elephant from a fly.
What you're doing here is creating an elephant from a fly.
yup - I'm big on quality control. 😁
Regardless, would you be fine with the proposed changes?
Some variables (along with their respective getters and setters) should be renamed:
transactionAmount
->amount
currencyID
->currencyId
economyTransactionType
->type