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
Right now it's not possible to have a dynamic array of reference types. A current workaround for this is to instead of reference types use their non-reference counterparts (uint64 for app, asset and address for Account). This is however not good enough as it requires workarounds in the SDKs to get the foreign references included which breakes the ease of use of the ATC/ABI.
Solution
Update pyteal to support dynamic reference types.
Urgency
It is currently hindering us from deploying production ready apps without some heavy workaround in the SDKs. It would be very nice to see this fixed.
The text was updated successfully, but these errors were encountered:
Problem
Right now it's not possible to have a dynamic array of reference types. A current workaround for this is to instead of reference types use their non-reference counterparts (uint64 for app, asset and address for Account). This is however not good enough as it requires workarounds in the SDKs to get the foreign references included which breakes the ease of use of the ATC/ABI.
Solution
Update pyteal to support dynamic reference types.
Urgency
It is currently hindering us from deploying production ready apps without some heavy workaround in the SDKs. It would be very nice to see this fixed.
The text was updated successfully, but these errors were encountered: