Problem/Motivation
Drupal 11 will release on Symfony 7. All prerequisites have landed so this is the issue where the upgrade will take place.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3432860
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3432860-update-to-sf7
changes, plain diff MR !7245
Comments
Comment #2
longwaveSymfony 7 requires PHP 8.2, 11.x currently still allows PHP 8.1, so postponing for now on #3413268: Add PHP 8.3 requirement to Drupal 11.0.x
Comment #4
longwaveComment #5
longwaveRunning into lots of "Deprecated NULL placeholder value for key (%name) in: "%name: this field cannot hold more than @count values.". This will throw a PHP error in drupal:11.0.0."
See #3431200: FieldItemList::getConstraints() incorrectly sets $maxMessage as TranslatableMarkup and #3054535-37: Discuss whether to decouple from Symfony Validator
Comment #6
longwavePushed a single commit from #3431200: FieldItemList::getConstraints() incorrectly sets $maxMessage as TranslatableMarkup which might be enough to get tests passing here.
Comment #7
longwaveSecond attempt where we only translate messages if we need to; in the case of NULL we use the default validation message.
Comment #8
longwaveThis is the bare minimum to get us to Symfony 7 - we should solve the validation messages issue across core in #3431200: FieldItemList::getConstraints() incorrectly sets $maxMessage as TranslatableMarkup.
Comment #9
catchHappy with doing #3431200: FieldItemList::getConstraints() incorrectly sets $maxMessage as TranslatableMarkup separately and after this lands, updating will make 11.x a much better testing target for contrib.
Comment #10
alexpottCommitted a65bbd5 and pushed to 11.x. Thanks!