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
For now, there is txSkelSomeRedeemer and txSkelEmptyRedeemer to pass redeemers to scripts in skeletons. There is also txSkelRedeemer which is a field accessor in skeletons (actually TxSkelRedeemer but the spirit is the same).
This is a bit confusing when using the user facing API. Completion pops up txSkelRedeemer easily instead of txSkelSomeRedeemer. Besides, the txSkel prefix should be used for field accessors only out of consistency.
I would advocate for dropping txSkel and renaming those to someRedeemer and emptyRedeemer. We could even just have redeemer and use () when empty (although we would lose a bit of abstraction).
The text was updated successfully, but these errors were encountered:
Very tiny nitpicking issue.
For now, there is
txSkelSomeRedeemer
andtxSkelEmptyRedeemer
to pass redeemers to scripts in skeletons. There is alsotxSkelRedeemer
which is a field accessor in skeletons (actuallyTxSkelRedeemer
but the spirit is the same).This is a bit confusing when using the user facing API. Completion pops up
txSkelRedeemer
easily instead oftxSkelSomeRedeemer
. Besides, thetxSkel
prefix should be used for field accessors only out of consistency.I would advocate for dropping
txSkel
and renaming those tosomeRedeemer
andemptyRedeemer
. We could even just haveredeemer
and use()
when empty (although we would lose a bit of abstraction).The text was updated successfully, but these errors were encountered: