Misc improvements

[macjuul]

• Refactored file names and imports

• Enforce file name format

• Initial work on reconnect support

• I have read the Contributing Guidelines

[ntorrey]

Yay for reconnect support! 🎉

[phisch]

@macjuul We just ran into an issue of our backend losing the connection to the database, and the backend had no way to even tell us about that. Anything using queries was just stuck indefinitely. We'd be super stoked about reconnect support. But is there anything we can do in the meantime until this gets merged? Even just being able to have a timeout that would let us know the connection is lost would be a big improvement.

[macjuul]

@macjuul We just ran into an issue of our backend losing the connection to the database, and the backend had no way to even tell us about that. Anything using queries was just stuck indefinitely. We'd be super stoked about reconnect support. But is there anything we can do in the meantime until this gets merged? Even just being able to have a timeout that would let us know the connection is lost would be a big improvement.

We are still debating on the internal implementation of a reconnect system, however in Surrealist I implemented this manually by subscribing to disconnect events and instantiating a new connection. Until official support is available this is likely the best approach

[phisch]

@macjuul Thanks for letting me know. But that would only work using rust, right? I don't see a way to subscribe to events in the TS SDK. (Hopefully I'm just blind)

Edit: I just saw there is .emitter on the connection. Not documented, but it looks like that would do it.

Edit 2: Yep, this seems to be that:

connection.emitter.subscribe("disconnected", async () => {
    // whatever
});