Move support for third-party plugins into separate plugins #898
Unanswered
BenParizek
asked this question in
Ideas
Replies: 2 comments
-
In Feed Me 1, third-party support was actually handled within the third-party plugin (via hooks). That approach has always seemed more logical to me, since the mechanics may change between plugin versions. Additionally, this would allow custom modules to register their own import mechanisms as well. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@BenParizek this is 100% the plan |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's nice that FeedMe supports several third-party plugins:
https://docs.craftcms.com/feed-me/v4/content-mapping/element-types.html
https://docs.craftcms.com/feed-me/v4/content-mapping/field-types.html#third-party
As individual plugin developers, sometimes we choose to have integrated support for other third-party plugins in the ecosystem.
However, now that FeedMe is a first-party plugin all third-party support should be moved to separate plugins that integrate with the documented FeedMe APIs, as not to favor some plugins in the ecosystem over others within a first-party tool.
While I prefer support for all third-party integrations to be handled via separate plugins via a documented API, if FeedMe supports some third-party plugins as a feature there should be a documented process for other third-party plugins to also be added as features.
Beta Was this translation helpful? Give feedback.
All reactions