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
Currently, it's only possible to get block events for a single block at a time. The access API currently supports getting event info for multiple blocks at once. We should try and leverage this functionality.
Suggest A Solution
We should either:
a) Add the ability to query multiple blocks at once using the current API. (i.e. put under the blocks sub command)
The advantage here is a large amount of reusable code
The disadvantage is that we'd actually not use the events API provided by the access API in a very optimized way
b) Add a new subcommand events which would simply query events.
The advantage would be a cleaner separation of intent, and better use of the AccessAPI,
The disadvantage would be that we'd now be able to query events from both the blocks and events sub commands, which could be somewhat confusing, as well as still not having the ability to query multiple blocks at once
I am likely to do a PoC of option b) and go from there.
The text was updated successfully, but these errors were encountered:
Issue To Be Solved
Currently, it's only possible to get block events for a single block at a time. The access API currently supports getting event info for multiple blocks at once. We should try and leverage this functionality.
Suggest A Solution
We should either:
a) Add the ability to query multiple blocks at once using the current API. (i.e. put under the
blocks
sub command)b) Add a new subcommand
events
which would simply query events.blocks
andevents
sub commands, which could be somewhat confusing, as well as still not having the ability to query multiple blocks at onceI am likely to do a PoC of option b) and go from there.
The text was updated successfully, but these errors were encountered: