v0.4.11

Changed

• Remove expectation of an IPv4 address and allow for IPv4 and IPv6.

v0.4.10

Added

• Signal handling on app websocket.

Changed

• Update deps to Holochain v0.2.7.
• Adapt admin and app websocket to new version of package holochain_websocket.

v0.4.9-rc.2

Added

• Signal handling on app websocket.

v0.5.0-dev.31

Changed

• BREAKING: The underlying package holochain_websocket changed. All websockets in this client follow the new connect function and take a socket address that implements ToSocketAddr instead of a URL String. Examples for the new parameter are "localhost:30000" and ([127.0.0.1], 30000). See trait ToSocketAddr.
• BREAKING: The attach_app_interface method of the AdminWebsocket now takes an additional parameter of type AllowedOrigins which specifies what origins are allowed to connect to the created app interface.

v0.5.0-dev.30

Changed

• BREAKING: The underlying package holochain_websocket changed. All websockets in this client follow the new connect function and take a socket address that implements ToSocketAddr instead of a URL String. Examples for the new parameter are "localhost:30000" and ([127.0.0.1], 30000). See trait ToSocketAddr.

v0.4.9-rc.1

Changed

• Update deps to Holochain v0.2.7-rc.1.
• Adapt admin and app websocket to new version of package holochain_websocket.

v0.5.0-dev.29

Removed

• BREAKING: The utilities crate, it is now replaced by signing built into the client. Please see the updated tests for examples of how to use this.
• BREAKING: sign_zome_call_with_client which was used internally but also exposed in the public interface. You probably don't need to call this but if you wish to for some reason then use one of the two new *Signer types, and convert them to a Arc<Box<dyn AgentSigner>>, then use the sign method to compute a signature. The logic to prepare the data to be signed is no longer public so you would have to set this up yourself following the sign_zome_call function in the signer module.

Added

• Capability to create zome call signing credentials with the AdminWebsocket using authorize_signing_credentials.
• ClientAgentSigner type which can store (in memory) signing credentials created with authorize_signing_credentials.
• LairAgentSigner which is analagous to the ClientAgentSigner but is a wrapper around a Lair client instead so that private keys are stored in Lair.
• from_existing method to the AppAgentWebsocket which allows it to wrap an existing AppWebsocket instead of having to open a new connection. This is useful if you already have an AppWebsocket but otherwise you should just use the connect method of the AppAgentWebsocket rather than two steps.

Changed

• BREAKING: AppAgentWebsocket::connect now takes an Arc<Box<dyn AgentSigner>> instead of a LairClient. The Arc<Box<dyn AgentSigner>> can be created from a .into() on either a ClientAgentSigner or a LairAgentSigner. Use the latter to restore the previous behaviour.
• BREAKING: AppAgentWebsocket::call_zome used to take a RoleName as its first parameter. This is now a ZomeCallTarget. There is a .into() which restores the previous behaviour. Now you can also pass a CloneCellId or a CellId, also using a .into(). Using CellId is stronly recommended for now. Please see the doc comments on ZomeCallTarget if you intend to use the other options.

v0.4.8

Added

• Capability to create zome call signing credentials with the AdminWebsocket using authorize_signing_credentials.
• ClientAgentSigner type which can store (in memory) signing credentials created with authorize_signing_credentials.
• AppAgentWebsocket to simplify making zome calls. It is a wrapper around a AppWebsocket but can be created directly.

Removed

• The utilities crate, it is now replaced by signing built into the client. Please see the updated tests for examples of how to use this.

v0.5.0-dev.28

Added

• Export AdminWebsocket::EnableAppResponse to be available downstream.

v0.4.7

Added

• Export AdminWebsocket::EnableAppResponse to be available downstream.