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
They must be able to be built client-side, such as from the trait definitions as it is today. For when the client has access into the external contract's src code, this builder can be generated by the external contract's src code itself, so the client would only need to import and then use the builder.
For builders prepared on specific impls, they can take advantage of the payable, or maybe gas = x attributes to eg. actually refrain from implementing payment option, or make a attached gas check to early panic (instead of making a call and then it panicking on the server contract)
Another related feature is to have a generic external contract call while also having a builder-pattern structure. This is mostly implemented in here (outdated) but it could use more design iteration.
The text was updated successfully, but these errors were encountered:
There are some discussions related to this, such as:
External Contract's methods can be represented by a builder, something like:
Or a current code example.
They must be able to be built client-side, such as from the trait definitions as it is today. For when the client has access into the external contract's src code, this builder can be generated by the external contract's src code itself, so the client would only need to import and then use the builder.
For builders prepared on specific impls, they can take advantage of the
payable
, or maybegas = x
attributes to eg. actually refrain from implementing payment option, or make a attached gas check to early panic (instead of making a call and then it panicking on the server contract)Another related feature is to have a generic external contract call while also having a builder-pattern structure. This is mostly implemented in here (outdated) but it could use more design iteration.
The text was updated successfully, but these errors were encountered: