There are at least a couple of initiatives related to uncluttering project top level dirs with configuration files for various tools by promoting use of the .config/ subdir.

• https://github.com/pi0/config-dir (see also `.config` dir support tracker pi0/config-dir#6)
• https://dot-config.github.io

These are not that popular yet, but it would be great if dprint could implement this, to help unclutter on its own part and help the initiatives gain general traction.

Basically, I think just searching for the filenames (that don't start with a dot) dprint currently searches to find its config in a .config/ subdir in addition to the current lookup mechanism (including when traversing upward) would be a nice implementation. No particular opinion about the precedence, but the set could be

• .config/dprint.jsonc
• .config/dprint.json
• (.config/.dprint.jsonc -- I don't think this is necessary, but I guess it would not hurt)
• (.config/.dprint.json -- I don't think this is necessary, but I guess it would not hurt)
• dprint.jsonc
• dprint.json
• .dprint.jsonc
• .dprint.json