I'm getting following error, when I am using get methods in the contracts in Vue.js app:

Uncaught (in promise) TypeError: Cannot read private member from an object whose class did not declare it
    at __classPrivateFieldGet (TonClient.js:17:94)
    at Proxy.runMethod (TonClient.js:53:25)
    at Proxy.callGetMethod (TonClient.js:68:21)
    at Object.get (TonClient.js:329:39)
    at DSocialNetworkMaster.getGetBlogsCount (tact_DSocialNetworkMaster.ts:1750:38)
    at Proxy.<anonymous> (openContract.js:38:47)
    at getLastBlogAddress (CreateBlog.vue:87:52)
    at goToNewBlogAddress (CreateBlog.vue:72:25)
    at callWithErrorHandling (runtime-core.esm-bundler.js:158:18)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:166:17)

Possibly, it also can be the case in other frameworks, but as far as I know Vue and JS private hash fields (TonClient.#api) have difficult relationships because of Proxies used by Vue. It might resolve the error, if we replace all hash fields with just private TS properties.

It would be useful if the status repo changed.
This can be stronger redirection in contrast to readme.
I see some who made a mistake

Which repository will be developed and supported in the long run https://github.com/ton-core/ton or https://github.com/ton-org/ton-core?

I see that on both of these are commits that are missing on the other. I think we should at least put a deprecation notice on one of them

Also do we now when ton-core/ton-core#33 will be released to npm?

Hello,

I am trying to exec callGetMethod from the browser and am getting this error:
Access to XMLHttpRequest at 'https://testnet.toncenter.com/api/v2/jsonRPC' from origin '...' has been blocked by CORS policy: Request header field x-ton-client-version is not allowed by Access-Control-Allow-Headers in preflight response.

I'm using apiKey for TonClient() function

Something like

["tuple", {"@type": "tvm.tuple", "elements": [{ "@type": "tvm.stackEntryNumber", "number": { "@type": "tvm.numberDecimal", "number": "1" }}]}]

or

[ 'list', { '@type': 'tvm.list', elements: [] } ]

is not supported currently.

It would be greate to have an option to make secretKey is optional for createTransfer for wallet contracts to have an option to create unsigned transfers for estimations.

The feature will use in OpenMask and Tonkeeper web

Transaction does not contain its own hash, only hash of previous transaction. It’s quite inconvenient, e.g in scenarios when one wants to persist transactions in database. Also toncenter’s response has it, though it’s not encoded in “data” field. Could you please add it?

1. Change to callGetMethod (or change TonClient to runMethod), if there's no good reason for them to be different.
2. Response should return a TupleReader, similar to TonClient

(To match TonClient)

Is there any plan to support "injecting" different network adapter to the TonClient constructer
as it seems it's not implemented

adapter?: AxiosAdapter; - is never used