130: Connect directly to websockify r=D4nte a=D4nte
To avoid websocket timeout issue
Resolves#123 (long term solutions are tracked in separate issues)
Co-authored-by: Franck Royer <franck@status.im>
126: Ensure that listeners are added only when waku is initialised r=D4nte a=D4nte
this removes the `Reached max listeners` error.
Co-authored-by: Franck Royer <franck@status.im>
118: Clean up WakuMessage API r=D4nte a=D4nte
121: Always trigger store query at connection r=D4nte a=D4nte
If no new messages are received, the rendering does not change
as dupe messages are filtered out.
122: Use provided API r=D4nte a=D4nte
Co-authored-by: Franck Royer <franck@status.im>
105: Group sequential messages from same sender into single group, reduce CSS padding, and don't repeat sender name and timestamp r=D4nte a=littlealex003
- **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
Feature
- **What is the current behavior?** (You can also link to an open issue here)
Resolves#86
Name and timestamp are printed for each message
Large amounts of space are used for each message
- **What is the new behavior (if this is a feature change)?**
Name and timestamp are only printed for first message from sender until someone else sends a message
Padding and margin around text eliminated to maximize screen real estate usage
Co-authored-by: Franck Royer <franck@status.im>
115: Connect to the test fleet r=D4nte a=D4nte
With `websockify` instance running on jdev and pointing to fleet node.
Co-authored-by: Franck Royer <franck@status.im>
95: Use off-the-shelf React Templates for UI r=D4nte a=littlealex003
- **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
Refactor
- **What is the current behavior?** (You can also link to an open issue here)
Custom React Material UI Implementation
- **What is the new behavior (if this is a feature change)?**
Off the shelf React Material Chat UI Implementation
Co-authored-by: littlealex003 <littlealex003@gmail.com>