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
Hey Team, I am working on flow testcases in js using flow-js-testing library. I am trying to pass AnyStruct as an argument for my transactions and scripts but I am unable to pass it.
I have already create an issue on flow-cadut you can see more details on that link. After more debugging I found that issue is occurring from @onflow/types as there is no any support for AnyStruct in flow types.
Issue To Be Solved
To resolve that issue, we need to add support for AnyStruct in flow types.
The text was updated successfully, but these errors were encountered:
AnyStruct is only a super-type of all non-resource types in Cadence. it is not possible to construct a value from AnyStruct type, and not possible to use AnyStruct as an argument for a script or transaction.
Yes I am agree with you that AnyStruct is the super-type of all non-resource types in Cadence, but I didn't understand your statement that
it is not possible to construct a value from AnyStruct type, and not possible to use AnyStruct as an argument for a script or transaction
I think fcl has the issue because of flow-types. I am working on that part and soon will complete it and create a PR. Once we have support for AnyStruct in flow/types than we can easily work flow-cadut to support it as an argument for transaction/scripts
Add support for type
AnyStruct
Hey Team, I am working on flow testcases in js using flow-js-testing library. I am trying to pass
AnyStruct
as an argument for my transactions and scripts but I am unable to pass it.I have already create an issue on flow-cadut you can see more details on that link. After more debugging I found that issue is occurring from @onflow/types as there is no any support for
AnyStruct
in flow types.Issue To Be Solved
To resolve that issue, we need to add support for
AnyStruct
in flow types.The text was updated successfully, but these errors were encountered: