a2044c61ae
We have three interactions with an extension's prefs module: - we import the module - we call its init() hook - we call its buildPrefsWidget() hook The first two are one-time actions where we expect most getCurrentExtension() calls (local imports, initTranslations() etc.). However it's still possible that the extension will use the utility function in buildPrefsWidget() as well, either directly or via other functions like getSettings(): Make sure getCurrentExtension() returns the correct extension in that case, not the last one whose preferences were initialized. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/873 |
||
|---|---|---|
| .. | ||
| extensionPrefs | ||
| gdm | ||
| misc | ||
| perf | ||
| portalHelper | ||
| ui | ||
| js-resources.gresource.xml | ||
| meson.build | ||
| portal-resources.gresource.xml | ||
| prefs-resources.gresource.xml | ||