Revert "v0.3.3 changes into main"

[davidhopkinson26]

Reverts #64

correcting for a squashed commit from develop. #64 was squashed which has resulted in commits reappearing in #78. Best way to preserve work appears to be to revert #64 and then re-apply changes in #78.

[davidhopkinson26]

failing linting checks due to reverting bugfix from #45. #78 should bring this change back into main and it is only linting so we should be safe to override the checks in this case

[adamsardar]

I agree that, whilst it isn't ideal to override the linter, commit history train wrecks can make for an unfortunate tangle. You're right that it's picking up on the issue solved here in #45. Agree that we can await #78 for restoration of lints (currently passing).

[adamsardar]

Practically impossible to review the squashed commits here as the individual commits have been lost. We should disable the ability to 'squash and merge' is possible; I don't see why you would do this at the stage of merge.

See: https://dev.to/wesen/squash-commits-considered-harmful-ob1