Closed awfulcooking closed 2 years ago
Looking good, thanks for this! Let me know when you think it's done.
I think we should merge this, test it, and release after a few days if all seems well. Then improve from there!
I'd rather test before merging, but in general this seems like a good fix for this issue, thanks for your work. As for a release, I gotta see, because I already have a new feature in master
(#263), so to make a v1.9.3 release for #283 would require reverting the feature and re-adding it after release. #283 is not a show-stopper bug, so I'm not sure if it merits its own release or not.
Also please see my reply above.
As for testing, it would probably be best to induce errors, like was done in #281, and make sure there are no UI issues.
Pushing commits to this branch, feel free to test / merge, or wait for more to come in.