# Deprecation patterns ignored while testing this module. Core's own
# core/.deprecation-ignore.txt is appended to this file by the phpunit
# job, so both sets apply; see .gitlab-ci.yml.
#
# Format: https://www.drupal.org/node/3285162
#
# Everything here belongs to a dependency or to core, never to kessai.
# A deprecation naming any of this project's namespaces, Drupal\kessai
# and Drupal\kessai_engine alike, is a real finding and belongs fixed,
# not ignored: the "Transaction object go out of scope" one this lane
# surfaced was fixed by committing explicitly, not by a pattern.
#
# cspell:disable
# drupal/consumers still uses an annotation for its entity type.
%Using @EntityType annotation for plugin with ID consumer is deprecated%

# Core 11.5 deprecates procedural code in a .module file, and key and
# consumers still ship one. Named per project, so that a .module file of
# kessai's own is never silenced here.
%Code in (key|consumers)\.module is deprecated%

# Forward-compatibility warnings raised by Symfony's DebugClassLoader
# against key and consumers. Core carries the same pattern for its own
# modules: the downstream project has to add the return types first.
# Only those two are listed; audit_trail raises none, and silencing a
# project we maintain would hide findings that belong fixed at the source.
%Method "Drupal\\[^"]+::[^"]+\(\)" might add "[^"]+" as a native return type declaration in the future\. Do the same in (?:implementation|child class) "Drupal\\(key|consumers)\\[^"]+" now to avoid errors or add an explicit @return annotation to suppress this message%

# Twig's own forward-compatibility notice about a core class.
%(Since twig/twig 3\.28: )?The "Drupal\\Core\\Template\\TwigSandboxPolicy::checkSecurity\(\)" method will (take a 4th|require a new)%
# cspell:enable
