From 317382f1b9eb20b498c641b7c6eae36c6a5a0032 Mon Sep 17 00:00:00 2001 From: rilaxik Date: Mon, 28 Oct 2024 08:54:27 +0000 Subject: [PATCH] plans --- RPC-%40-0.2.1.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/RPC-%40-0.2.1.md b/RPC-%40-0.2.1.md index e046c49..4f6d480 100644 --- a/RPC-%40-0.2.1.md +++ b/RPC-%40-0.2.1.md @@ -251,6 +251,14 @@ These should be clear enough themselves, in other cases refer to here - ``NO_BROWSER`` - throws on client if you failed to specify valid browser for it to refer to when calling browser - ``EVENT_RESPONSE_TIMEOUT`` - throws in Promise (rejects) when failed to receive a response data from called environment. You may not always want to receive it at all, for now it just works like this. Prefer adding ``catch`` on your events +# Plans (todo) +Estimate plans for release +- [ ] Register multiple events at once +- [ ] Implement Batch call multiple events +- [ ] Opt out of event response to avoid error handling +- [ ] Separate browser dev environment (currently uses unknown) +- [ ] Improve error handling + # License MIT License