豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content

Always use plugin constructor instead of a soft requirement in features #19747

@pomek

Description

@pomek

📝 Provide a description of the improvement

In the past, because of the DLL nature, each package had to be separate, and imports between feature packages were not allowed.

Since we are going to drop support for DLL builds (see #17779), could we bring back proper imports to improve DX?

Example:

public static get requires() {
return [ EmojiRepository, Typing, 'Mention' ] as const;
}

Definition of Done

  • Review all of the soft requirements and decide if they can be replaced with a plugin constructor instead.
  • Review ESLint rules that were blocking imports between packages. They are no longer needed.
  • Review the documentation to remove the soft requirement section (if defined).
  • Changes should be made in both repositories.

Technical details

  • Tree shaking.
  • Circular dependencies.

Metadata

Metadata

Assignees

Labels

squad:platformIssue to be handled by the Platform team.type:improvementThis issue reports a possible enhancement of an existing feature.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions