-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Remove deprecated endpoints and enhanced transaction information by expanding Buy
and Sell
resources
#89
base: master
Are you sure you want to change the base?
Conversation
* Now the Buy and Sell objects have been subsumed under the 'expanded' transaction object. ShouldSerializeBuy() and ShouldSerializeSell() methods are used by Newtonsoft to conditionally deserialize transaction data. They're automatically called. If they return FALSE, then the corresponding property is not serialized. For example, if a property is named Foo (the C# property name), then the corresponding method ShouldSerializeFoo() will dictate whether the corresponding 'Foo' property is serialized.
* Add a call to ListTransactionsAsync and GetTransactionAsync, respectively, to pass the ?expand=all query param. This allows us to obtain full transaction and fees information.
At 15:33 hours MST on 01/05/2024, I am moving on to fix the |
* Also fixed the spelling of 'WithdrawlTests' to 'WithdrawalTests'
Commit: 8e6fa2f
As of 15:48 hours MST on 01/05/2024, I have made all the unit tests in |
As of 15:59 hours MST on 01/05/2024, I am now moving on to get all the |
As of 16:09 hours MST on 01/05/2024, I found that the unit test |
Commit: 078b3d2c76a32ae2f1fbb3ed4952cba4cb675fa1
As shown in Figure 1, all the |
As of 16:17 hours MST on 01/05/2024, I deleted the entire |
As of 16:21 hours MST on 01/05/2024, all the tests are passing except the I am pushing commit f9d111e which deletes the |
@bchavez I am going to close this PR and recommend you merge it. I have gotten AppVeyor to stop yelling at me! :-) |
@bchavez Whoops, I think that closing the PR is not advisable since it will be difficult for you to merge it. |
@bchavez Well, I am not sure what exactly the error
and those like it in AppVeyor mean, but could have something to do with this PR targeting Net 7.0 and not 6.0. Anyhow, can you please look into this? I would appreciate you considering this PR for merge. Thank you. |
log.txt I am unsure of what to do at this juncture. It builds just fine on my PC, and all the unit tests (except the ones I cannot run due to not having the |
@bchavez I had an inspiration. Upon looking at the AppVeyor logs I found where it was locking down the versions of the Consulting the I pushed commit 58681d9, which includes these changes. |
@bchavez In the AppVeyor log, I see:
Other than that, I give up. I ask for your assistance. I simply do not know F# and I think I need to prevail upon yourself to fix the config for the new .NET targets. Thank you! |
As of 16:54 hours MST on 01/05/2024, I decided to re-target the .NET COre multi-targeting of the |
Thanks for the investigation and PR. Yes, the problem is the F# A more recent example of Basically, migrating to NUKE build is the first step in getting this repo running/building again. The NUKE build migration will have to be done in a separate PR when I can get to it. As you can see, there's a bit of maintenance work to keep things going. |
Just merged PR #91 to get the repo building again. |
Please review my PR and merge what you deem appropriate! I tried to be super thorough in my comments and I tried to be prodigious about writing down which Commit SHA each comment goes with. |
Removed the following endpoints, as they are totally offline (calling them gives a
HTTP 410 Gone
response:Buys
Sells
Users
and their associated unit tests.
Update the
List Transactions
andShow Transaction
methods in theTransactions
endpoint, along with theTransaction
model, to expandBuy
andSell
resources inline.