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

**URL:** <https://platform.jetbrains.com/t/how-to-inform-built-in-platform-plugin-that-my-file-type-is-not-theirs/3582>\
**Category:** IntelliJ Platform\
**Created:** [January 26, 2026, 2:57pm UTC](https://platform.jetbrains.com/t/how-to-inform-built-in-platform-plugin-that-my-file-type-is-not-theirs/3582 "2026-01-26T14:57:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Nicholas\_Hubbard](https://avatars.discourse-cdn.com/v4/letter/n/9fc348/32.png) [@Nicholas\_Hubbard](https://platform.jetbrains.com/u/Nicholas_Hubbard)\
**Post date:** [January 26, 2026, 6:24pm UTC](https://platform.jetbrains.com/t/how-to-inform-built-in-platform-plugin-that-my-file-type-is-not-theirs/3582/4 "2026-01-26T18:24:35Z")

</div>

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.

---

_[View the full topic](https://platform.jetbrains.com/t/how-to-inform-built-in-platform-plugin-that-my-file-type-is-not-theirs/3582)._