v0.17.0

What's Changed

• Allow Protobuf v5 dependency by @FZambia in #102

Full Changelog: v0.16.0...v0.17.0

v0.16.0

What's Changed

• Allow usage of protobuf v4, drop protobuf v2 by @FZambia in #100

Full Changelog: v0.15.1...v0.16.0

v0.15.1

What's Changed

• Support Fossil delta compression by @FZambia in #97

Full Changelog: v0.15.0...v0.15.1

v0.15.0

What's Changed

• Update web_socket_channel, min Dart SDK is now 3.3 #91
• Support headers emulation in web context - so it's possible to pass custom connection headers to the backend when using Centrifugo v6 and connect proxy. Also added setHeaders method to update headers #92.

This release changes headers in ClientConfig from Map<String, dynamic> to Map<String, String>. This is a breaking change, but it must not cause huge troubles beyond a simple refactoring.

Usages of dart.html were removed in this release. Also some internal optimizations were done to allocate less when constructing Protobuf command data.

Full Changelog: v0.14.1...v0.15.0

v0.14.1

What's Changed

• Add renew connection data callback by @Holofox in #88

Full Changelog: v0.14.0...v0.14.1

v0.14.0

What's Changed

• connInfo and chanInfo for join/leave events by @hetao29 #84

New Contributors

• @hetao29 made their first contribution in #84

Full Changelog: v0.13.0...v0.14.0

v0.13.0

• Relax Protobuf dependency requirements to be >=2.0.0 <4.0.0 instead of ^3.0.0

v0.12.0

What's Changed

• Fix websocket usage in web env (fixes The method 'sendByteBuffer' isn't defined for the type 'WebSocket' error), add simple web example #85

Full Changelog: v0.11.0...v0.12.0

v0.11.0

What's Changed

• Update protobuf dependency from ^2.0.0 to ^3.0.0
• Update SDK requirement to '>=2.19.0 <4.0.0'

Full Changelog: v0.10.0...v0.11.0

v0.10.0

What's Changed

Breaking change! This release changes the semantics of working with connection tokens described in Centrifugo v5 release post.

Previously, returning an empty token string from getToken callback resulted in client disconnection with unauthorized reason.

Now returning an empty string from getToken is a valid scenario which won't result into disconnect on the client side. It's still possible to disconnect client by throwing a special UnauthorizedException from getToken function.

And we are putting back setToken method to the SDK – so it's now possible to reset the token to be empty upon user logout.

Full Changelog: v0.9.4...v0.10.0