# Deprecations this project accepts, ON TOP OF the installed core's own list.
#
# This file holds ONLY what core's list does not. CI concatenates
# <installed core>/.deprecation-ignore.txt with this one at job time — see
# .gitlab-ci.yml — so whichever core minor a job installs contributes its own
# entries and this file never has to track them.
#
# An earlier cut of this file WAS a snapshot of core 11.4.6's list. That broke
# the `previous minor` job immediately: core 11.3.16's list is not 11.4.6's —
# it carries a Request::get entry 11.4 no longer needs, and the snapshot
# silently dropped it. A per-version list cannot be a checked-in copy of one
# version. Concatenating at job time is the fix; this file is the delta.
#
# THE RULE: every entry here is somebody else's debt. Nothing this module owns
# belongs in this file — fix that instead.

# --- ui_patterns (contrib) -------------------------------------------------
#
# Core already ignores this exact Twig forward-compatibility warning for its
# OWN extension, with the comment "in order to let contrib modules make their
# necessary fixes first". Core's pattern is scoped to
# Drupal\Core\Template\TwigExtension, so contrib raising the identical warning
# from its own extension is not covered.

%Method "Twig\\Extension\\ExtensionInterface::(getFunctions|getFilters)\(\)" might add "array" as a native return type declaration in the future. Do the same in implementation "Drupal\\ui_patterns\\Template\\TwigExtension" now to avoid errors or add an explicit @return annotation to suppress this message%
%Since symfony/validator 7\.4: Support for evaluating options in the base Constraint class is deprecated\. Initialize properties in the constructor of Drupal\\ui_patterns\\Plugin\\Validation\\Constraint\\RequiredArrayValuesConstraint instead\.%

# --- Drupal core on the PREVIOUS MINOR, under symfony 7.4 ------------------
#
# These are core's own constraint classes, and they are in NEITHER core 11.3's
# ignore list nor 11.4's — because core 11.3 predates symfony/validator 7.4 and
# the CI composer install resolves the newer symfony against it. 11.4 fixed the
# classes; 11.3 will not be changed for it.
#
# Scoped to Drupal\Core deliberately: the same warning from ui_patterns is
# listed above on its own, and from this module it would fail the run, which is
# the point.

%Since symfony/validator 7\.4: Support for evaluating options in the base Constraint class is deprecated\. Initialize properties in the constructor of Drupal\\Core\\[A-Za-z\\]+Constraint instead\.%
%Since symfony/validator 7\.4: Support for passing the choices as the first argument to Drupal\\Core\\[A-Za-z\\]+Constraint is deprecated\.%

# --- droost, and this one has an expiry date -------------------------------
#
# FIXED AT SOURCE in droost 85a3730, which migrates droost_requirements to the
# OOP hook and marks the procedural one #[LegacyRequirementsHook]. This
# module's floor is `drupal/droost: ^2.0.0-alpha5@alpha`, which resolves to the
# alpha5 TAG, and alpha5 predates the fix — verified by unpacking the published
# tarball.
#
# DELETE THIS ENTRY once droost cuts a release containing 85a3730 and this
# module's floor moves to it.

%droost_requirements without a #\[LegacyRequirementsHook\] attribute is deprecated in drupal:11\.3\.0 and removed in drupal:13\.0\.0%

# --- Core entries ONE minor lists and the other does not -------------------
#
# Neither core list is a superset of the other, so concatenation alone leaves a
# version-shaped hole. Measured:
#
#   BlockManager::getSortedDefinitions  in 11.4's list, NOT in 11.3's
#   Request::get                        in 11.3's list, NOT in 11.4's
#
# In practice each core only triggers what its own list covers, so neither hole
# fires today. Carrying both here anyway makes the outcome independent of which
# minor a job installs, and a pattern that never matches costs nothing —
# which is the same reason core's own unreachable entries are left alone.

%The "(?:Drupal\\Core\\Layout\\LayoutPluginManagerInterface|Drupal\\Core\\Block\\BlockManager)::get(?:Sorted|Grouped)Definitions\(\)" method will require a new "string \$label_key" argument in the next major version of its interface%
%Since symfony/http-foundation 7\.4: Request::get\(\) is deprecated, use properties ->attributes, query or request directly instead\.%
