[Refactor] Get rid of control variables

[panleone]

Abstract

Idea: Get rid of the control variables that we have in the code, like #syncing, #isFetchingLatestBlocks, isCreatingTx (maybe there are more?).

This is done by creating a wrapper class LockableFunction that "simulates c++ RAII"

[netlify]

✅ Deploy Preview for cheery-moxie-4f1121 ready!

Name	Link
🔨 Latest commit	b8a414c
🔍 Latest deploy log	https://app.netlify.com/sites/cheery-moxie-4f1121/deploys/662673f20be5670008df43a9
😎 Deploy Preview	https://deploy-preview-341--cheery-moxie-4f1121.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[JSKitty]

tACK 98814ec

I didn't expect to like this too much, but it makes a lot of sense and is generally cleaner to maintain or debug.

One maintenance downside to potentially think about (JS issue again lol): on functions that return anything, this might remove the type-safety of JSDoc, as I don't think the type information will be preserved through lockableFunction, thoughts?

Fortunately all current instances of lockableFunction do not return anything, so this is only a future concern if we end up using it for anything with a return type.

[Duddino]

Add the parenthesis or the expect isn't run

[Duddino]

tACK