A user can import Inspections with “clean import = false” and break up the configuration between two or more files, but the UI and pretty much all related infrastructure for Inspection configuration works under the assumption that the config is determined by exactly one file. Unless users keep track of it themselves there is no way for them to retrieve or view any info about the previous files which outline their configuration.

Since there will always be some upper limit on the size we can import for a singular config file, breaking up the config across multiple files is our best bet for ensuring that very large projects can be supported by inspections. Even if this weren’t the case, we shouldn’t allow a situation where essential info becomes invisible to the users. We should probably start thinking about how we could refactor the config UI/backend to persist configuration info across multiple files.