Feature/minor docs fixes (#223)

* webassembly: fixing example directory name in README

* rust client: fixing what I suspect is a typo in a type name

* Fixing wasm build instructions

Author: futurechimp

clients/desktop/src/client/mod.rs

@@ -29,8 +29,9 @@ use gateway_client::{GatewayClient, SphinxPacketReceiver, SphinxPacketSender};
 use gateway_requests::auth_token::AuthToken;
 use log::*;
 use nymsphinx::chunking::split_and_prepare_payloads;
-use nymsphinx::DestinationAddressBytes;
-use received_buffer::{ReceivedBufferMessage, ReconstructeredMessagesReceiver};
+use nymsphinx::{Destination, DestinationAddressBytes};
+use received_buffer::{ReceivedBufferMessage, ReconstructedMessagesReceiver};
+
 use tokio::runtime::Runtime;
 use topology::NymTopology;
 
@@ -52,7 +53,7 @@ pub struct NymClient {
     input_tx: Option<InputMessageSender>,
 
     // to be used by "receive" function or socket, etc
-    receive_tx: Option<ReconstructeredMessagesReceiver>,
+    receive_tx: Option<ReconstructedMessagesReceiver>,
 }
 
 #[derive(Debug)]

clients/desktop/src/client/received_buffer.rs

@@ -31,13 +31,13 @@ pub(crate) type ReceivedBufferRequestSender = mpsc::UnboundedSender<ReceivedBuff
 pub(crate) type ReceivedBufferRequestReceiver = mpsc::UnboundedReceiver<ReceivedBufferMessage>;
 
 // The channel set for the above
-pub(crate) type ReconstructeredMessagesSender = mpsc::UnboundedSender<Vec<Vec<u8>>>;
-pub(crate) type ReconstructeredMessagesReceiver = mpsc::UnboundedReceiver<Vec<Vec<u8>>>;
+pub(crate) type ReconstructedMessagesSender = mpsc::UnboundedSender<Vec<Vec<u8>>>;
+pub(crate) type ReconstructedMessagesReceiver = mpsc::UnboundedReceiver<Vec<Vec<u8>>>;
 
 struct ReceivedMessagesBufferInner {
     messages: Vec<Vec<u8>>,
     message_reconstructor: MessageReconstructor,
-    message_sender: Option<ReconstructeredMessagesSender>,
+    message_sender: Option<ReconstructedMessagesSender>,
 }
 
 #[derive(Debug, Clone)]
@@ -68,7 +68,7 @@ impl ReceivedMessagesBuffer {
         guard.message_sender = None;
     }
 
-    async fn connect_sender(&mut self, sender: ReconstructeredMessagesSender) {
+    async fn connect_sender(&mut self, sender: ReconstructedMessagesSender) {
         let mut guard = self.inner.lock().await;
         if guard.message_sender.is_some() {
             // in theory we could just ignore it, but that situation should have never happened
@@ -149,7 +149,7 @@ impl ReceivedMessagesBuffer {
 pub(crate) enum ReceivedBufferMessage {
     // Signals a websocket connection (or a native implementation) was established and we should stop buffering messages,
     // and instead send them directly to the received channel
-    ReceiverAnnounce(ReconstructeredMessagesSender),
+    ReceiverAnnounce(ReconstructedMessagesSender),
 
     // Explicit signal that Receiver connection will no longer accept messages
     ReceiverDisconnect,

clients/desktop/src/websocket/handler.rs

@@ -15,7 +15,7 @@
 use super::types::{BinaryClientRequest, ClientRequest, ServerResponse};
 use crate::client::{
     received_buffer::{
-        ReceivedBufferMessage, ReceivedBufferRequestSender, ReconstructeredMessagesReceiver,
+        ReceivedBufferMessage, ReceivedBufferRequestSender, ReconstructedMessagesReceiver,
     },
     topology_control::TopologyAccessor,
     InputMessage, InputMessageSender,
@@ -265,7 +265,7 @@ impl<T: NymTopology> Handler<T> {
         }
     }
 
-    async fn listen_for_requests(&mut self, mut msg_receiver: ReconstructeredMessagesReceiver) {
+    async fn listen_for_requests(&mut self, mut msg_receiver: ReconstructedMessagesReceiver) {
         loop {
             tokio::select! {
                 socket_msg = self.next_websocket_request() => {

clients/webassembly/README.md

@@ -14,7 +14,7 @@ See our [docs](https://nymtech.net/docs).
 
 ### Demo
 
-There's a demo web application in the `www` folder. To run it, first make sure you've got a recent `npm` installed, then follow the instructions in its README.
+There's a demo web application in the `js-example` folder. To run it, first make sure you've got a recent `npm` installed, then follow the instructions in its README.
 
 ### Developing