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
I generated types using taq generate
When I try to display a status field that is a variant type, it did not display, so I debugged it and I found that typing does not match
๐ Steps to Reproduce?
use a ligo variant : export type STATUS = ["ACTIVE"] | ["RECOVERING", address, timestamp] | ["DEAD"]; on a contract storage
deploy this contract with a status RECOVERING
generate the types on a dapp and try to display the status + the embedded address and the timestamp.
Instead of expected field 0 and 1 , the values are stored on fields 3 and 4
๐ฅ Status (Internal Taqueria Team Use Only)
๐ What happened?
I generated types using
taq generate
When I try to display a status field that is a variant type, it did not display, so I debugged it and I found that typing does not match
๐ Steps to Reproduce?
use a ligo variant :
export type STATUS = ["ACTIVE"] | ["RECOVERING", address, timestamp] | ["DEAD"];
on a contract storagedeploy this contract with a status RECOVERING
generate the types on a dapp and try to display the status + the embedded address and the timestamp.
Instead of expected field 0 and 1 , the values are stored on fields 3 and 4
๐ชต Relevant log output
๐ How impactful is this bug?
๐ค Notable but managable
โฑ๏ธ Prevalance
No response
๐ป Operating System
Windows -> WSL
๐ธ๏ธ System Architecture
x64
๐ฎ Taqueria Version
0.50.0
๐ฟ Node.js Version
v18.19.1
โ๏ธ Contact Details
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: