-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show block-level events in block details #990
Conversation
Deployed to Cloudflare Pages
|
dbe10db
to
c4b2960
Compare
c4b2960
to
881a9c6
Compare
cde7268
to
caba9e7
Compare
6c173a2
to
34fb4fb
Compare
We decided to do the tweaking of the event filter in a separate PR. |
} | ||
|
||
// eslint-disable-next-line @typescript-eslint/no-redeclare | ||
export type EventFilterMode = (typeof EventFilterMode)[keyof typeof EventFilterMode] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this + export const EventFilterMode = {
work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On is a type, the other is a const. TS compiler is smart enough to figure out which one we want in each situation. (The type is actually eliminated during the transpilation phase, so in the JS we only have the const.)
In any case, this is not something I came up with here, we already have a similar solution for Layer
and other things, too.
34fb4fb
to
3126e3e
Compare
W.I.P. because filtering out tx-level events is done on the client
2398743
to
51e2e75
Compare
51e2e75
to
b8c35b0
Compare
Built on top of #991 for some refactoring.Requires (and includes) #893 in order to avoid crashing on new event types.Design is here.
Can we tested with this path:
/testnet/sapphire/block/3038913