1. You shouldn't create another gsettings instance in line 1191-1195 to disconnect. The instances you created in the enable should be used in disable as well. Also they should get nulled out in disable. 2. What's the reason for using `Gio.Settings` in line 1209? You already have it in `gsettings` (line 1170 `extension.js`). 3. This one also has the unnecessary comments as mentioned in the version 18 review. The best practice for multi versioning package is to create different branches in your repo.

@JustPerfection: For #3, the comment method is my workflow, unique branches will cause greater effort in the CI/CD process, and it's a method I have seen in may other extensions. The keybinding file for instance is used elsewhere. Is there a reason this is getting rejected as an extension for code specifics vs broken functionality? I didn't think there were specific guidelines for code structuring extensions, but happy to follow it if there are policies documented somewhere. As for 1 & 2, will address those and resubmit, thank you for catching them.

Actually for #2 I don't follow the question. Line 1170 gets settings for the current extension, while line 1209 checks if the default Ubuntu tile extension is loaded and what it's settings are.

For #3 I can actually update my CI to remove the lines vs comment, so should be able to clean that up pretty easily, thanks.

For #2 it's ok then. #3 is just a recommendation but at least remove the unnecessary comments instead of adding `//` for the packages you are sending here.

Sounds great, thanks, will submit a new version shortly.

Just to be sure on #1, the variables mentioned are local inside `enable` and `disable`. Is the requirement to make them global variables? (That's what I'm doing now).

You can make them global. Also null them in disable.

Will do (they're nulled if you expand the diff above, but am putting them in a container object anyway). Thanks again.