-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invert checkboxes #147
Comments
It is now in this way because when we add a new service with a release the new service is automatically shown. |
Yes, but it's not logically correct. When you insert a new service, just insert is as "checked" instead of "unchecked" |
How you can detect that is a new service so with the update become checked automatically? |
By checking its presence in the storage. If it's not there, it wasn't present on the last save. Thus, it is likely a new service. |
@Mte90 Or just you set "checked" as default. It's the same of the unchecked logic |
It's breaking insofar, as the logic (the meaning of checked) is flipped. Thus, it has to be communicated somehow to users upgrading to the new version. |
This is the big problem as the extension is built to be simple so to do that we need to implement a lot of stuff. To implement this we need to implement a backport solution that doesn't break anything. |
I don't know if it is the case to close that ticket as after years I didn't got any support request about it. |
Do you pay to have opened issues? 🤔 |
It was just a way to updated the ticket to get people find it for hacktoberfest 😂 |
Instead of select checkboxes you want to disable it would be better select those you want to enable
The text was updated successfully, but these errors were encountered: