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
The most significant problem after enabling this in the project is:
src/tx/builder/schema.ts:583:17 - error TS4109: Type arguments for 'SchemaTypes' circularly reference themselves.
583 type TxSchema = SchemaTypes<typeof txSchema>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/tx/builder/schema.ts:586:13 - error TS2456: Type alias 'TxUnpacked' circularly references itself.
586 export type TxUnpacked = TxSchema['TxUnpacked'];
~~~~~~~~~~
It is important to be compatible with this option because it is enabled by default in some environments, like VS code and ts-node. Currently, it breaks the sdk types in a way
Object literal may only specify known properties, and 'payload' does not exist in type 'Omit<SpendOptions, "onNode" | "onAccount" | "onCompiler"> & Partial<Omit<SpendOptions, "onAccount"> & { onAccount: OnAccount; }>'.
13 await aeSdk.spend(1, aeSdk.address, { payload: 'ba_test' });
error TS2339: Property 'encodedTx' does not exist on type 'TxUnpacked & { tag: Tag.SignedTx; }'.
Property 'encodedTx' does not exist on type 'TxUnpackedAccount1 & { tag: Tag.SignedTx; }'.
20 const { tag } = unpackTx(tx, Tag.SignedTx).encodedTx;
The text was updated successfully, but these errors were encountered:
similar to #1706
The most significant problem after enabling this in the project is:
It is important to be compatible with this option because it is enabled by default in some environments, like VS code and
ts-node
. Currently, it breaks the sdk types in a wayThe text was updated successfully, but these errors were encountered: