Hey all, with potential future refactoring: I want...
# supabase-kt
j
Hey all, with potential future refactoring: I wanted to ask if there is something you feel is missing in supabase-kt, or where the library can be improved further (syntax, features, docs, integrations, etc.)? Offline support and type generation is already in the backlog, but will not come in the near future sadly.
🦗 1
🚀 1
h
I wonder if there’s any refactoring to error handling. As of now the lib mostly throw exceptions, this seems not so right as when we know it’s expected the error, we should somehow model it and let client handle the error. Exeptions are for unexpected cases. This would reduce complexity for client when handle errors. Reference: Phylosophy of software design of John Outsterhout Chapter 10: Define errors out of existence Quick note: https://github.com/alysivji/notes/blob/main/software-engineering/philosophy_of_software_design.md#chapter-10-define-errors-out-of-existence