gnome-shell/lint/eslintrc-shell.yml

rules:
  camelcase:
    - error
    - properties: never
      allow: [^vfunc_, ^on_]
  consistent-return: error
  eqeqeq:
    - error
    - smart
  key-spacing:
    - error
    - mode: minimum
      beforeColon: false
      afterColon: true
  prefer-arrow-callback: error

overrides:
  - files: js/**
    excludedFiles:
      - js/portalHelper/*
      - js/misc/extensionUtils.js
    globals:
      global: readonly
      _: readonly
      C_: readonly
      N_: readonly
      ngettext: readonly
  - files: subprojects/extensions-app/js/**
    globals:
      _: readonly
      C_: readonly
      N_: readonly
lint: Convert eslint JSON to YAML gjs has changed its configuration to YAML, so switch to that format to keep syncing possible. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/818 2019-08-19 13:20:55 -04:00			`rules:`
			`camelcase:`
			`- error`
			`- properties: never`
			`allow: [^vfunc_, ^on_]`
			`consistent-return: error`
ci: Switch ESLint rule eqeqeq to smart mode This allows comparisons like != null and == null while still erroring on other usages of == and !=. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2363> 2022-07-05 12:13:15 -04:00			`eqeqeq:`
			`- error`
			`- smart`
lint: Convert eslint JSON to YAML gjs has changed its configuration to YAML, so switch to that format to keep syncing possible. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/818 2019-08-19 13:20:55 -04:00			`key-spacing:`
			`- error`
			`- mode: minimum`
			`beforeColon: false`
			`afterColon: true`
			`prefer-arrow-callback: error`

			`overrides:`
			`- files: js/**`
			`excludedFiles:`
			`- js/portalHelper/*`
extensionUtils: Add gettext convenience helpers We have initTranslations() for binding an extension's gettext domain, but nothing to help with using gettext from an extension. Such help would be useful though, as an extension that calls textdomain() like a normal application would inadvertently changes the default domain for the whole gnome-shell process. Instead, extensions have to use domain-specific versions of the gettext functions: ```js const Gettext = imports.gettext.domain('my-extension'); const _ = Gettext.gettext; ``` Make this a bit easier by adding those functions directly to the extensions object when initTranslations() is called, then expose helper functions for calling them. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2594 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1941> 2020-04-11 20:45:55 -04:00			`- js/misc/extensionUtils.js`
lint: Convert eslint JSON to YAML gjs has changed its configuration to YAML, so switch to that format to keep syncing possible. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/818 2019-08-19 13:20:55 -04:00			`globals:`
			`global: readonly`
			`_: readonly`
			`C_: readonly`
			`N_: readonly`
			`ngettext: readonly`
extensions-app: Move Extensions app to new subproject The Extensions app code is now independent enough from the rest of the code base to move it to its own subprojects, like we did for the extensions-tool. This allows for stand-alone builds of the app, which we are about to use for distributing it as flatpak. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1133 2019-11-30 21:01:02 -05:00			`- files: subprojects/extensions-app/js/**`
			`globals:`
			`_: readonly`
			`C_: readonly`
			`N_: readonly`