Should "file_types" settings be part of "languages"?

[albedoa]

Problem statement: The "file_types" setting contains key/value pairs that are a natural fit for — and that I would expect to find in — the "languages" setting. The values are arrays of filename patterns that determine the language settings that are used. They look like "languages" settings:

"file_types": {
  "JSON": ["flake.lock"],
  "JSONC": [
    "**/.zed/**/*.json",
    "**/zed/**/*.json",
    "**/Zed/**/*.json",
    "tsconfig.json",
    "pyrightconfig.json"
  ]
},
"languages":
  "JSON": {
    "prettier": {
      "allowed": true
    }
  },
  "JSONC": {
    "prettier": {
      "allowed": true
    }
  }
},

Further, the UI and command for selecting which settings to use is called the "language selector".

Solution proposal: Make "file_types" a key on each language in the "languages" setting:

"languages":
  "JSON": {
    "file_types": ["flake.lock"],
    "prettier": {
      "allowed": true
    }
  },
  "JSONC": {
    "file_types": [
      "**/.zed/**/*.json",
      "**/zed/**/*.json",
      "**/Zed/**/*.json",
      "tsconfig.json",
      "pyrightconfig.json"
    ],
    "prettier": {
      "allowed": true
    }
  }
},

I am mostly curious about the reasons behind this design decision or whether this proposal has been considered before. I realize that it is fairly low-stakes and probably not worth a breaking change at this time.

I got here from the Contributing page, which says:

The best way to propose a change is to start a discussion on our GitHub repository.

Though the only categories are Q&A and Show and tell. Thank you!

[albedoa]

I am realizing that each set of settings in "languages" represents overrides of first-level settings. I had thought that the key/value pairs were settings that were only found within the "languages" settings. Now it makes sense why "file_types" doesn't belong in there.