Problem/Motivation

While working on #3519934: [2.2.0] Add ui_patterns_field_widgets sub-module, we noticed there is an issue with the Drupal 12 upgrade (and the move from Symfony 7 to Symfony 8.0).

See this commit: https://git.drupalcode.org/project/ui_patterns/-/merge_requests/372/diff...

Proposed resolution

  1. Change the way we are constructing constraints
  2. Change all info.yml to declare Drupal 12 compatibility.

Is it a breaking change? Is it preventing us to support both Drupal 11 and Drupal 12? Do we need to move to UI PAtterns 3?

Comments

pdureau created an issue. See original summary.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented

From Core 11.4.0: https://www.drupal.org/node/3555534 / https://git.drupalcode.org/project/drupal/-/commit/2f82880037313b2948a59...

From Core 12.0.0 : https://www.drupal.org/node/3569092 / https://git.drupalcode.org/project/drupal/-/commit/aea47fe1b2bf794554898...

So I think if we increase core requirements to 11.4.0 it will be ok.

grimreaper’s picture

grimreaper
Primary language French
Location France 🇫🇷
commented
Related issues: +#3555534: Since symfony/validator 7.4: Support for evaluating options in the base Constraint class is deprecated. Initialize properties in the constructor instead., +#3569092: Update method signatures for addConstraint() and ConstraintManager::create() and remove HasNamedArguments use