-
Notifications
You must be signed in to change notification settings - Fork 261
Conversation
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.
reviewed most of the files. mostly looks good -- will look at the last few files remaining soon.
this review has more changes than I was expecting so it's taking a little longer -- although they all seem warranted so thanks for make these changes. will try and take a look at the rest of the files as soon as possible but it will likely be after the kelp hackathon is kicked off this week because there's a lot of stuff to be done before I can kick that off.
Added a few comments inline about pointers, rest looks good so far.
No worries, please take your time. It is essential that the changes do not introduce any bugs so it is a good call to delay on this a bit till you have more bandwidth. |
…cture It was invalid because it was fetch before it existed and therefore was incomplete.
avoids threading errors through in this situation where really there should be no reason for an error from the delete offer op, althrough ideally we should thread the error through
closes #269
This PR covers part of the work required to update Kelp to use the new stellar Go sdk. This PR focuses on changing the transaction builder package from
build
totxnbuild
.This PR also changes the usage of
clients/horizon
in some places that could not be changed in #204. In particular, these two files were changed.../gui/backend/upsert_bot_config.go
.../gui/backend/autogenerate_bot.go
With these changes, Kelp should not have any instance of the deprecated
build
andclients/horizon
packages.This PR is based off the branch in #204, please review that before this.
Nikhil's list of outstanding issues to check:
baseAmount
andquoteAmount
numbers that are divided by 10^7. Example:0.00015000
instead of1500.0000000
when the other log lines use the correct value of1500.0000000
txnbuild.Operation
references inapi/*
so we don't bump major version number and create a new PR for this API change to be merged later