- Issue created by @thejimbirch
- πΊπΈUnited States traviscarden
Yes, I think we should deprecate
seo_checklist_optional_modules
. It think it was mostly created for convenience for evaluators and for local development. I would never recommend using it in production. I think recipes present some much more interesting possibilities.If anyone is using the module in production, we can't remove it without potentially breaking their site. And we don't want to move the dependencies to our main
composer.json
, which would exacerbate the problem in several respects. I think it would be best to remove it in a 6.x branch where we can introduce a lot of the other major changes that seem to be coming.If the version constraints in the module pose a problem in the meantime, we can loosen or even eliminate them (e.g., change
^2
to>=2.0
or even*
). -
traviscarden β
committed f31458b6 on 5.2.x authored by
thejimbirch β
Issue #3473560 by thejimbirch: Deprecate submodule...
-
traviscarden β
committed f31458b6 on 5.2.x authored by
thejimbirch β
- πΊπΈUnited States traviscarden
Oh, interesting. I haven't done this before either, but it looks right based on the documentation you pointed to. Fixed.
Automatically closed - issue fixed for 2 weeks with no activity.