I see this is based on the pixel-saver extension. Should it replace pixel-saver because it is no longer developed or something or is the focus different? What is the relationship with pixel-saver and why the fork?

Hi! I actually intended to explain a bit here, and then forgot to do so... I started the work on this some months ago to add some options to Pixel Saver. I proposed a PR upstream, and then realized most of them were ignored over time, especially if it's for implementing new features/configuration (which the author seems to be against anyway, based on the README). You can see as an example my PR upstream: https://github.com/deadalnix/pixel-saver/pull/115, which I closed a few moments ago. As I mention there, I was against forking, since there is duplication of effort (and also it's a shame, as Pixel Saver is already well-known). However, there isn't much communication from the author and he mentioned a few times that he doesn't have much time to review PRs. Hence, the fork. Thanks for you attention and inquiries!

Ok. From what I can glean the original author seems hesitant to merge changes and we will review your extension on its own merits without suggesting merging the extensions or your fork becoming the canonical version of pixel-saver. Please allow some time for the review since the codebase is already substantial.

Thank you for the quick feedback. I understand if it takes some time, there is no rush. Cheers. -Fran

Closing this review request, please refer to the new upload: https://extensions.gnome.org/review/7161. I included a few small fixes, plus a more standardized style.