gnome-shell/js
Ray Strode 7e5ee2c282 extensionSystem: Get rid of _enabled boolean optimization
At the moment a session mode either allows extensions or it doesn't.
If it allows extensions, then the entire available list of
configured extensions get enabled as soon as the session mode is
entered.

Since enabling or disabling extensions is an all or nothing situation,
the code tracks whether extensions are already enabled when entering
the session mode, and if so, avoids iterating through the extension list
needlessly. It does this using a boolean named _enabled.

In the future, the extensions themselves will be given some say on
whether or not they should be enabled in a given session mode. This
means, the configured extension list may contain extensions that
shouldn't be enabled for a given session mode, and the _enabled boolean
will no longer be appropriated.

This commit drops the _enabled boolean optimization.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1967>
2021-10-14 18:40:53 +00:00
..
dbusServices dbusServices/screencast: Handle pipeline failures gracefully 2021-06-09 15:21:35 +00:00
gdm gdm: Remove pending fingerprint verification failure 2021-04-28 17:23:01 +00:00
misc inputMethod: Clear preeditStr before reset 2021-09-30 17:12:02 +00:00
perf perf: Add basic run tests 2020-08-12 15:43:39 +00:00
portalHelper portalHelper: Replace Soup.URI with GLib.Uri 2021-08-25 01:54:07 +02:00
ui extensionSystem: Get rid of _enabled boolean optimization 2021-10-14 18:40:53 +00:00
js-resources.gresource.xml init: Set console log domain 2021-09-01 14:55:47 +00:00
meson.build extensions-app: Move Extensions app to new subproject 2020-03-27 23:33:30 +00:00
portal-resources.gresource.xml js: Remove unused files from resources 2020-03-09 13:18:48 +00:00