Richard Moore

This won’t be changed in v5, but I am working on a more expressive API for v6.

Thanks @zemse. I’ll look into this shortly.

I've made a few attempts to implements this, and it is far more involved than a simple change. The contract filtering wasn't really designed to allow multiple topic0. I'll make...

I don't think this can be an issue necessarily with ethers; does Vue use some sort of compilation or transpiring step, like using Babel? The TypeScript compiler should find any...

Which provider are you using?

You may need to use keep-alive pings to keep the provider alive (e.g. by calling something like getBlockNumber periodically). The WebSocket provider does not reconnect and re-subscribe to events in...

This is definitely not backwards compatible. I'll need to think about it for a bit whether it will go into the next minor bump. What scenarios do you already have...

You are changing the signature from `string` to `string | object`. Changing *any* signature is no longer backwards compatible. Which is why it requires a minor bump.

Right. Perhaps forwards-compatible is the right phrase. Yes, backwards breaking changes are major version changes. The main point where a signature change matters is in methods, where widening a type...

In this case none, I just meant in general, widening a **method** signature type breaks backwards compatibility. Widening a **function** signature type should be safe. :)