- Issue created by @alorenc
- Status changed to Closed: works as designed
4 months ago 3:11pm 2 September 2024 - π§πͺBelgium dieterholvoet Brussels
Thereβs no reason to add a composer.json file if all dependencies are Drupal modules that are already defined in the info.yml file. Otherwise, when updating dependencies, the version needs to be changed in two places. This is often forgotten.
Is there a reason you want to drop support for Drupal 8? I donβt see why we would need to do that.
Please also stick to one feature request/task per issue to keep MRβs easily reviewable and revertable, and to make sure changelogs contain a full list of changes with motivation for each one. Code style changes, Drupal/PHP version upgrades and the addition of a Gitlab CI template belong in separate issues.
- π΅π±Poland alorenc Wolsztyn, π΅π±
d8 is the end of live. I thought the best would be to drop that to make code cleaner. Create a new version of the module and use new features from PHP 8.1, not 8.3 as we want to support older environments
- Issue was unassigned.