| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Info: Something failed but it's not really an error. These errors
mostly only get logged
- Warning: Something failed to complete the operation, but it's not
critical for the functioning. E.g. state changes (maybe a button gets
pressed twice quickly, NO-OPS, e.g. disconnecting but no active server)
- Error: Something failed that was needed to complete for the
functioning of the app (e.g. a server is down and cannot be connected to)
|
|
This is problematic as we do not want to remove already fully added servers!
|
|
|
|
|
|
|
|
This removes the FSM from being imported and thus used in other
internal packages such as `oauth` or `server`. The benefit is that it
becomes much easier now to reason about the FSM as it's only used in
the public package. Additionally, we do not have to re-initialize the
server and the oauth structure with the FSM pointer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- /disconnect is now called
- A new state is added (DISCONNECTING) that waits for the disconnect to complete
- A helper function is exposed (InFSMState) that can be used by clients to see in which state they are in
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The reason behind this is that we then do not have to pass a lot to
each function. Logging inside internal packages is less useful as we
want to let them return errors and only log in the 'public' facing API
or let the client decide
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Let clients serialize data to a file themselves
|
|
|
|
|
|
|