v0.0.3

What's Changed

• fix(presence): fix presence not synchronizing states properly by @timadevelop in #7

New Contributors

• @timadevelop made their first contribution in #7

Full Changelog: v0.0.2...v0.0.3

0.0.2

Full Changelog: v0.0.1...v0.0.2

2024-4-5

Breaking changes

• before a channel connects, data is now undefined rather than null

• basic useEvent data caching

  The last response from any useEvent is cached across all instances. This means that if if you recieve any event for a channel topic, and for example the useEvent hook unmounts, once it remounts, it will instantly load the last recieved data and state for the given event.

  Previously if you recieved an event and the hook unmounted and remounted, the data stored in the useEvent hook was lost and you have needed to recieve the event again to get the data back.

  Once you leave a channel using leave() all cached data for the useEvent will be cleared.

Additional changes

• useChannel now accepts a passive option

  passive will instruct the channel to wait for another instance of useChannel to connect with the necessary params and then once a connection is made, the passive channel will connect itself. See the js docs for more information.

Release 0.0.1

see Changelog

What's Changed

• 0.0.1 by @Jdyn in #6