Plugin naming restrictions

IntelliJ Platform
1

Hi,

What are the hard restrictions on plugin naming?
Can the name of a project be in the name? Like “MySuperExtension for PyCharm”?

Bye,
jo

2

Your plugin name as it appears on the Marketplace cannot include “JetBrains” or other brandings by JetBrains. You can, however, call your project whatever you like.

For example, I have a project called Pyrefly for PyCharm. The suffix “for PyCharm” is to differentiate it from the actual tool, Pyrefly (@facebook/pyrefly), just in case I ever make a fork called @InSyncWithFoo/pyrefly. The Marketplace name of the plugin is just “Pyrefly”.

3

More details here: Best practices for listing your plugin | JetBrains Marketplace Documentation

4

The suffix “for PyCharm” is to differentiate it from the actual tool

This seems to contradict this practice from the docs:

  • Don’t: Include “JetBrains” or supported JetBrains products in the name.

But if you got it accepted like that, it might indicate a suggestion and not a hard restriction.

5

Please also:

  • Don’t Use the word “Plugin” in the name.
  • Don’t Use Emoji or symbols in the name.
  • No Marketing slogans and prices/offerings in names
  • Don’t use special symbols to visually copy other plugin names, users will get confused in search, we enforce name uniqueness
1 Like
6

@chbndrhnns Let me rephrase: The “for PyCharm” suffix is a part of my own naming convention for my repositories/projects. On the other hand, what JetBrains cares about is the Marketplace name of the plugin (i.e., the name it is published under).

For the project in question, its name, as I call it, is Pyrefly for PyCharm; I don’t call it Pyrefly because that name also refers to the tool I’m providing integration for. However, to the Marketplace and its users, the plugin is called Pyrefly, with no suffix.

1 Like