Remove Experimental SDC Dependency

It this is what we want then we should also require that this module uses Drupal 10.3 instead of 10.1. If someone WAS using Drupal 10.1 then they would need to enable the experimental module.

The README does specify that the module can be used with Drupal 10.1 or 10.2 but the experimental SDC module needs to be enabled manually.

Just re-tagging with the official tag :-)

Could see either side on this one, but I'd rather not restrict the audience for this module again. It does add a potential hiccup for pre 10.3 users, but I think the benefit of a wider potential audience outweighs the risk.

Removing SDC doesn't appear to have an impact on newer version of Drupal. (works in starshot as is). Perhaps if it were to cause a problem in newer version of Drupal, that is when we should consider removing it.

In other words, what is the harm in keeping our requirements as is?

If you enable through the UI it will give a warning about enabling experimental modules. And generally I’d imagine it isn’t uncommon for projects to not allow experimental modules. It also can’t be disabled because it is an explicit dependency.

Neither situation is perfect, but I still think we’re better off removing the dependency.

It's fair.

Here's what I think:

1. We create a new version that's should be the one that people get for new Drupal versions.
2. We keep the current version "stuck in the past", when sdc was experimental.

@cosmicdreams are you talking about a regular tagged release here, or a major version / breaking change?

on drupal 11 things with sdc not only look odd but are actively blocking the install. if you are trying to install same page preview on drupal 11.0.1, the composer require step works but you are unable to actually install 2.1.4 because of sdc is missing.

liam morland → made their first commit to this issue’s fork.

Rebased

Automatically closed - issue fixed for 2 weeks with no activity.