mirror of
https://github.com/logos-messaging/js-waku.git
synced 2026-01-07 16:23:09 +00:00
### Changed - **Breaking**: Websocket protocol is not automatically added anymore if the user specifies a protocol in `libp2p.modules` when using `Waku.create`. - **Breaking**: Options passed to `Waku.create` used to be passed to `Libp2p.create`; Now, only the `libp2p` property is passed to `Libp2p.create`, allowing for a cleaner interface. - Examples (cli chat): Use tcp protocol instead of websocket. ### Added - Enable access to `WakuMessage.timestamp`. - Examples (web chat): Use `WakuMessage.timestamp` as unique key for list items. - Doc: Link to new [topic guidelines](https://rfc.vac.dev/spec/23/) in README. - Doc: Link to [Waku v2 Toy Chat specs](https://rfc.vac.dev/spec/22/) in README. - Examples (web chat): Persist nick. - Support for custom PubSub Topics to `Waku`, `WakuRelay`, `WakuStore` and `WakuLightPush`; Passing a PubSub Topic is optional and still defaults to `/waku/2/default-waku/proto`; JS-Waku currently supports one, and only, PubSub topic per instance.
3.8 KiB
3.8 KiB
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Unreleased
0.6.0 - 2021-06-09
Changed
- Breaking: Websocket protocol is not automatically added anymore if the user specifies a protocol in
libp2p.moduleswhen usingWaku.create. - Breaking: Options passed to
Waku.createused to be passed toLibp2p.create; Now, only thelibp2pproperty is passed toLibp2p.create, allowing for a cleaner interface. - Examples (cli chat): Use tcp protocol instead of websocket.
Added
- Enable access to
WakuMessage.timestamp. - Examples (web chat): Use
WakuMessage.timestampas unique key for list items. - Doc: Link to new topic guidelines in README.
- Doc: Link to Waku v2 Toy Chat specs in README.
- Examples (web chat): Persist nick.
- Support for custom PubSub Topics to
Waku,WakuRelay,WakuStoreandWakuLightPush; Passing a PubSub Topic is optional and still defaults to/waku/2/default-waku/proto; JS-Waku currently supports one, and only, PubSub topic per instance.
0.5.0 - 2021-05-21
Added
- Implement Waku v2 Light Push protocol.
- Expose
Directionenum from js-waku root (it was only accessible via the proto module). - Examples (cli chat): Use light push to send messages if
--lightPushis passed. - Examples (cli chat): Print usage if
--helpis passed.
0.4.0 - 2021-05-18
Added
callbackargument toWakuStore.queryHistory(), called as messages are retrieved ; Messages are retrieved using pagination, and it may take some time to retrieve all messages, with thecallbackfunction, messages are processed as soon as they are received.
Changed
- Testing: Upgrade nim-waku node to v0.3.
- Breaking: Modify
WakuStore.queryHistory()to accept oneObjectinstead of multiple individual arguments. getStatusFleetNodesreturn prod nodes by default, instead of test nodes.- Examples (web chat): Connect to prod fleet by default, test fleet for local development.
- Examples (cli chat): Connect to test fleet by default, use
--prodto connect to prod fleet.
Fixed
- Expose
EnviromentandProtocolenums to pass togetStatusFleetNodes.
0.3.0 - 2021-05-15
Added
getStatusFleetNodesto connect to Status' nim-waku nodes.
Changed
- Clarify content topic format in README.md.
Removed
- Unused dependencies.
0.2.0 - 2021-05-14
Added
WakuRelay.getPeersmethod.- Use
WakuRelay.getPeersin web chat app example to disable send button.
Changed
- Enable passing
strings toaddPeerToAddressBook. - Use
addPeerToAddressBookin examples and usage doc. - Settle on
js-wakuname across the board. - Breaking:
RelayDefaultTopicrenamed toDefaultPubsubTopic.
0.1.0 - 2021-05-12
Added
- Add usage section to the README.
- Support of Waku v2 Relay.
- Support of Waku v2 Store.
- Node Chat App example.
- ReactJS Chat App example.
- Typedoc Documentation.