You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank all contributors for their code contributions.
During the use process, I have some thoughts and suggestions, as follows:
Problem: V2 and V2 API are different. They are provided separately because of their differences. For example, GetTransactionsV2 and TranasactionsV3, TranasactionsV3 can query a transaction for a TxHash. The two have different functions. When they are combined, the query function for TxHash is hidden.
Solution: You can add V2, V3, etc. to the API method name, so that developers can use the official V2 and V3 methods freely without the encapsulation causing some functions to be castrated.
The text was updated successfully, but these errors were encountered:
Hi, thanks for the suggestion, you can add this implementation via pull request, if you want to see it faster in TonSDK.Net, otherwise, i dont plan to make any new update in incoming month
witter-deland
changed the title
Suggesston: split http api v2 & v3 in tonclient
Suggesston: split v2 & v3 & lite api in tonclient
Jun 3, 2024
witter-deland
changed the title
Suggesston: split v2 & v3 & lite api in tonclient
Suggesstion: split v2 & v3 & lite api in tonclient
Jun 4, 2024
First of all, thank all contributors for their code contributions.
During the use process, I have some thoughts and suggestions, as follows:
Problem: V2 and V2 API are different. They are provided separately because of their differences. For example, GetTransactionsV2 and TranasactionsV3, TranasactionsV3 can query a transaction for a TxHash. The two have different functions. When they are combined, the query function for TxHash is hidden.
Solution: You can add V2, V3, etc. to the API method name, so that developers can use the official V2 and V3 methods freely without the encapsulation causing some functions to be castrated.
The text was updated successfully, but these errors were encountered: