-
Notifications
You must be signed in to change notification settings - Fork 678
feat: add Filecoin.ChainNotify method and Filecoin support websockets and subscriptions
#712
feat: add Filecoin.ChainNotify method and Filecoin support websockets and subscriptions
#712
Conversation
f2cffe9 to
9f88b4e
Compare
| // We have to use type any instead of ReturnType<typeof connector.parse> | ||
| // on `payload` because Typescript isn't smart enough to understand the | ||
| // ambiguity doesn't actually exist | ||
| let payload: any; |
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.
😢
Is the ambiguity caused by just having multiple chains? Or is it specific to the Filecoin API implementation?
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.
It's ambiguity caused by having multiple chains, not specific to Filecoin. It's likely that typescript is smart enough with some more convoluted types lol, but I didn't take the appropriate time to learn how to do the complex types yall have set up, because the current types do not support it. I personally don't think it's worth the time for this small functionality
8801d55 to
fabba07
Compare
b8ec20f to
ffcef74
Compare
db1c5e8 to
482c72a
Compare
ffcef74 to
d398425
Compare
acec01f to
50aa0aa
Compare
d398425 to
86984ad
Compare
86984ad to
e4997b1
Compare
|
We're postponing these reviews until later |
This PR is part of #694 (although most Lotus applications want to use WebSockets)
This supports the Chain Explorer feature in the https://github.com/filecoin-shipyard/filecoin-network-inspector example
This PR also resolves #692: