-
Notifications
You must be signed in to change notification settings - Fork 16
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
chore: move express-request and transaction reversal to builder pattern #88
Conversation
receiver identifier type
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.
Added some comments on the amount
field for the request and builder structs, as a simple workaround, we should consider switching to u32
to avoid potential validation errors. This would mean removing the #[builder(setter(into))]
attribute on the amount
field for the builder structs
The only floating point number accepted by Safaricom is <num>.0
, so to avoid these kinds of errors, let's always send whole numbers to Safaricom
I noticed this was a problem while working on #90
express_request.rs and transaction_reversal.rs
Hey @itsyaasir, I'm looking into the why the CI workflow is failing |
I think |
Closes #20
Closes #43
Closes #24