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
{{ message }}
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
It has been brought to my attention that the indexer can only capture an event if it has an ID associated with it, potentially in the form of a struct.
I may have misunderstood.
If it is not currently possible to capture events such as
log(5u64)
and instead we must do
log(SomeStruct { field:5u64 })
then that is an unintuitive UX limitation.
I expect to be able to log any type and capture it in the indexer rather than be limited to wrapping it into a struct.
The text was updated successfully, but these errors were encountered:
It has been brought to my attention that the indexer can only capture an event if it has an ID associated with it, potentially in the form of a struct.
I may have misunderstood.
If it is not currently possible to capture events such as
and instead we must do
then that is an unintuitive UX limitation.
I expect to be able to log any type and capture it in the indexer rather than be limited to wrapping it into a struct.
The text was updated successfully, but these errors were encountered: