aboutsummaryrefslogtreecommitdiffstats
path: root/TODO.md
diff options
context:
space:
mode:
authorLibravatar cel 🌸 <cel@bunny.garden>2025-02-12 06:19:02 +0000
committerLibravatar cel 🌸 <cel@bunny.garden>2025-02-12 06:19:02 +0000
commit8e6aa698b35f62dcd3d5c627f39dde53d0b1154d (patch)
tree98251f104eb32caf740f1ed76b10684bcfb90971 /TODO.md
parentec41f1d4ff07a00223b6ed34fc5b65c38d3cd535 (diff)
downloadluz-8e6aa698b35f62dcd3d5c627f39dde53d0b1154d.tar.gz
luz-8e6aa698b35f62dcd3d5c627f39dde53d0b1154d.tar.bz2
luz-8e6aa698b35f62dcd3d5c627f39dde53d0b1154d.zip
reconnection supervisor command
Diffstat (limited to 'TODO.md')
-rw-r--r--TODO.md42
1 files changed, 28 insertions, 14 deletions
diff --git a/TODO.md b/TODO.md
index 48e0556..47c86d9 100644
--- a/TODO.md
+++ b/TODO.md
@@ -2,22 +2,36 @@
## next
-ci/cd: doc generation
-feature: error handling on stream according to rfc6120
-docs: jid
-docs: jabber
-docs: starttls
-docs: sasl
-docs: resource binding
-feature: starttls
-feature: sasl
-feature: resource binding
-
-## in progress
-
-feature: logging
+feat(luz): everything in rfc6120 and rfc6121
+ feat(luz): handle_online
+ feat(luz): handle_offline
+ feat(luz): handle_stanza
+ feat(luz): database
+ feat(luz): error handling on stream according to rfc6120
+ feat(luz): send message
+ feat(luz): receive message
+ feat(luz): retreive messages stored in database
+ feat(luz): get roster (online and offline)
+ feat(luz): set roster
+ feat(luz): reconnect supervisorcommand
+feat: thiserror everywhere
+feat(luz): proper stanza ids
+test: proper tests
+ci: doc generation
+docs(jid): jid
+feat(peanuts): derive macros for IntoElement and FromElement
+docs(jabber): connection, starttls, sasl, binding, bound_stream, etc.
+feat: proper logging for everything basically
+feat(luz): passwordprovider trait, to avoid storing password in struct
+feat(luz): auto-reconnect state stored in luz actor, for if e.g. server shut down
+refactor(luz): dealing properly with all the joinsets and joinhandles
+feat(peanuts): some kind of way to configure the reader and writer to log the raw xml written to the stream, probably by having a method that allows you to add a log writer to them. will need to investigate some kind of log namespacing.
+feat(jabber): storing resource within the bound_stream connection
## done
+feature: starttls
+feature: sasl
+feature: resource binding
feature: jabber client connection
feature: jid