{"version":"2.1.248","anchor":"settings-scopes-now-carry-an-explicit-operator-or-repo-rank","canonical_anchor":"settings-scopes-now-carry-an-explicit-operator-or-repo-rank","heading":"Settings scopes now carry an explicit operator-or-repo rank","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/settings-scopes-now-carry-an-explicit-operator-or-repo-rank","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Settings scopes now carry an explicit operator-or-repo rank\n\nSettings sources now carry explicit precedence ranks and whether they belong to you or the repo.\n\n**What**\n\nThe list of places settings can come from now records, for each one, whether it belongs to the operator or to the repository and where it sits in precedence: policy settings rank 0, flag settings 1, user settings 2, with project and local settings marked as repo-owned. This replaces a flat name lookup.\n\n**Details**\n\n- New maps translate between the short names `user`, `project` and `local` and the internal settings keys.\n\n**Evidence**\n\n`{ kind: \"operator\", rank: 0 }`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}