Add plugin namespaces RFC

[jorisw]

See RFC.

[alexandrebodin]

Hi @jorisw Can you change the link tu the preview of the rfc insteand :)

[jorisw]

Like this?

[alexandrebodin]

Thanks for this RFC.

Two points:

• Your RFC don't take into account name collision in the code if we strip the org name from the plugin (e.g strapi.plugins.xxxx) what xxx will it be ? If we have two plugins with the same name in two different orgs ?
• In v4 we will certainly move to a config to enable plugin and not use the npm package directly to offer more flexibility. (to be confirmed) In that case this would be solved pretty easily with some like what (eslint, gatsby ...) does with their plugin config

[jorisw]

Your RFC don't take into account name collision in the code if we strip the org name from the plugin (e.g strapi.plugins.xxxx) what xxx will it be ? If we have two plugins with the same name in two different orgs ?

Actually my proposal deals with that in two ways:

• The short term proposal converts package with name @my-org/strapi-plugin-lolcat-generator to plugId @my-org/lolcat-generator (instead of lolcat-generator)
• The long term proposal converts package with name @my-org/strapi-plugin-lolcat-generator to { namespace: '@my-org', pluginId: 'lolcat-generator'}.

In v4 we will certainly move to a config to enable plugin and not use the npm package directly to offer more flexibility. (to be confirmed) In that case this would be solved pretty easily with some like what (eslint, gatsby ...) does with their plugin config

Sounds good. Plug-ins indeed should themselves provide their namespace and name on the long run. I've found reading package.json to be quite a hacky approach.

When is v4 due?

[derrickmehaffy]

When is v4 due?

I don't believe we have a hard date for that yet.

[strapi-cla]

All committers have signed the CLA.

[alexandrebodin]

Hi, going to close this RFC as we addressed this in v4