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
After much deliberation with developers, it became apparent that many of them preferred Method Chaining instead of the current implementation.
Currently, transactions can be signed and sent like so:
client:=NewGlowClient().Start()
collector, err:=client.CreateDisposableAccount()
iferr!=nil {
panic(err)
}
txRes, err:=client.NewTxFromFile(
TxPath("account_setup"),
*collector, // account passed as an arg
).SignAndSend()
This implementation would allow for Method Chaining like this:
client:=NewWrappedGlowClient() // instantiate wrapped clientcollector, err:=wclient.CreateDisposableActor() // create an "Actor" (an account wrapped with a reference to a client)iferr!=nil {
panic(err)
}
// can create, sign and send a transaction with method chaining from an ActortxRes, err:=collector.NewTxFromFile(
TxPath("account_setup"),
).SignAndSend()
Let's create a wrapped client package to allow for method chaining. This will give developers substantially more flexibility when developing with Glow.
The text was updated successfully, but these errors were encountered:
After much deliberation with developers, it became apparent that many of them preferred Method Chaining instead of the current implementation.
Currently, transactions can be signed and sent like so:
This implementation would allow for Method Chaining like this:
Let's create a wrapped client package to allow for method chaining. This will give developers substantially more flexibility when developing with Glow.
The text was updated successfully, but these errors were encountered: