REST response and typing mismatch? about tatum-js

[samuelsramko]

Hey @silasbw, the reason why we are using the different naming of the field is the SDK being a first-class citizen for us now. We are and will be integrating multiple different sources for data and unifying them inside the SDK. It means that the SDK DTOs might look different than the API responses, which is perfectly correct. If you choose to use the API for this integration, you are of course free to do it. It's just the SDK which has different format.

[silasbw]

We're using the SDK, so is your recommendation we do, like:

// The SDK types don't match the actual shape returned by the REST API: 
//    The REST API returns NftTokenDetail.type (not NftTokenDetail.tokenType)
// @ts-ignore
const tokenType = response.data[0].type

[samuelsramko]

O I see, Thats something else. @Hathoriel, @hehe100596 or @alexloiko can you guys check this out pls?

[samuelsramko]

Probably some typo during refactoring…

[Hathoriel]

Hello yes @samuelsramko I will look on it.
Thanks for finding the issue @silasbw

[Hathoriel]

👋 Hello @silasbw
The issue should be fixed in the version 3.1.7.
Hope this helps!
Have a nice day.

[silasbw]

Thanks @Hathoriel 🙌