Bjarte S. Karlsen
Bjarte S. Karlsen
This should be joined in with the interaction-template initiative I think.
I have looked through overflow and these are the methods I use in there ``` script.go 78: result, err := o.Services.Scripts.Execute( event_fetcher_old.go 156: blockHeight, err := e.OverflowState.Services.Blocks.GetLatestBlockHeight() 180: blockEvents, err...
I have some code that transactions resolved to a network. So it geneerates the final form in the blocto repo and not the middle step. It was easier that way....
You want me to contribute this back to flowkit?
For me the interesting aspect here is really if it worth it. Both dapper and blocto have approved tx repos that work differently. This will just be a third way...
@bluesign just made me aware of this. Will this not break _a lot of code_. Today I store Capabilities inside structs very often and this change will make this impossible....
Right now there is no event emitted when storage is stored/loaded or when a link/unlink operation happends. It would be very powerful if that is the case. One constant problem...
@turbolent do you have any hints on how to go forward here, There is quite a lot boilerplate and I am not sure I have finished it all.
My usecase for this is to add context to events, since in some scenarios it is really hard to add "the other side" to an event.