How to inform built-in platform plugin that my file type is not theirs

IntelliJ Platform
1

My plugin looks at YAML files in a specific named directory with a specific file name format.
If I test the plugin in the free edition of IDEA 2025.3.2, only my plugin activates, but when I activate the sandbox edition with my work license, the Kubernetes plugin tries to kick in and puts a bunch of errors in these files alongside my plugin.

I know I can add # nok8s to the top of these files to tell the Kubernetes plugin to back off, but I’d prefer for my end users to not need this crutch in the first place. Is there a way to inform the Kubernetes plugin of this?

I’ve also noticed that the Kubernetes plugin throws a lot of errors when I open and close my files in the sandbox instance of the IDE, but I’m not sure if those are just sandbox issues, or warnings about real functionality in a non-sandboxed instance.

2

com.intellij.fileTypeOverrider probably could help, but the risk is users will lose all YAML features if you reassign file type to a completely unrelated file type.

We probably could also implement a check on plugin side that if a YAML file is not YAMLFileType then Kubernetes plugin would not try to inspect it.

4

I agree on the FileTypeOverrider. I have one already for another file type in the project.

Because I ran into some issues early on in the plugin development with directly inheriting YAMLFileType, my file type implements LanguageFileType(YAMLLanguage.INSTANCE), FileTypeIdentifiableByVirtualFile, PlainTextLikeFileType instead.

I know there’s no standard folder name for Kubernetes configs, but I’d also consider either blocking my folder name (I can message you privately about it), or blocking based on a file name format; we have a strict layout that our plugin looks for.