Are there any precedents in this space? I’m trying to draw parallels with things like IntelliJ checkstyle inspections etc. The config sources are: * files in a user’s home directory (user configs) * files in the project (project configs) * within the file (e.g. # noqa) * IDE settings (the ones in question) I’m going to take linting as the example here. Obviously “within the file” should win always, so let’s dismiss those settings. My thinking is that project configs are configured to be verified at CI/build time. They basically say, “I don’t care who works on the project, they need to conform to this style guide”. User configs (in their home directory) are there for when project configs don’t exist. You’re working on a project that doesn’t have any style preference explicitly checked in, so you’re going to apply your own preferences for your work only. So project configs override user configs when running the linter. IDE settings then exist to customise the user’s editing experience. In applying these settings they are choosing to ignore what the project says, and go with their own style. So they should override the project settings. * If you want to default project configurations, you should do so in your user configs. * if you want those configs verified at build time, they should be checked in to the project * if you want to ignore the project settings and apply your own, then you configure your editor. At least that was my train of thought implementing this. I could probably argue for the other way as well though! So keen to hear your thoughts.