Closed (fixed)
Project:
Name Field
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 Oct 2026 at 22:23 UTC
Updated:
18 Oct 2026 at 13:45 UTC
Jump to comment: Most recent
------ -----------------------------------------------------------------------
Line name.install
------ -----------------------------------------------------------------------
34 Avoid calling Symfony\Component\Yaml\Yaml::parse() directly. Use
\Drupal\Component\Serialization\Yaml::decode() instead, which handles
exceptions consistently and applies the correct parse flags.
🪪 drupal.symfonyYamlParse
41 Avoid calling Symfony\Component\Yaml\Yaml::parse() directly. Use
\Drupal\Component\Serialization\Yaml::decode() instead, which handles
exceptions consistently and applies the correct parse flags.
🪪 drupal.symfonyYamlParse
61 Avoid calling Symfony\Component\Yaml\Yaml::parse() directly. Use
\Drupal\Component\Serialization\Yaml::decode() instead, which handles
exceptions consistently and applies the correct parse flags.
🪪 drupal.symfonyYamlParse
706 Avoid calling Symfony\Component\Yaml\Yaml::parse() directly. Use
\Drupal\Component\Serialization\Yaml::decode() instead, which handles
exceptions consistently and applies the correct parse flags.
🪪 drupal.symfonyYamlParse
712 Avoid calling Symfony\Component\Yaml\Yaml::parse() directly. Use
\Drupal\Component\Serialization\Yaml::decode() instead, which handles
exceptions consistently and applies the correct parse flags.
🪪 drupal.symfonyYamlParse
733 Avoid calling Symfony\Component\Yaml\Yaml::parse() directly. Use
\Drupal\Component\Serialization\Yaml::decode() instead, which handles
exceptions consistently and applies the correct parse flags.
🪪 drupal.symfonyYamlParse
------ -----------------------------------------------------------------------
------ ---------------------------------------------------------------------
Line src/Service/NameFormatterService.php
------ ---------------------------------------------------------------------
96 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
97 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
------ ---------------------------------------------------------------------
------ ---------------------------------------------------------------------
Line src/Service/NameOptionService.php
------ ---------------------------------------------------------------------
51 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
52 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
------ ---------------------------------------------------------------------
------ ---------------------------------------------------------------------
Line tests/src/Unit/Plugin/Field/FieldFormatter/NameFormatterTest.php
------ ---------------------------------------------------------------------
161 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
162 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
------ ---------------------------------------------------------------------
------ -----------------------------------------------------------------------
Line tests/src/Unit/Plugin/diff/Field/NameFieldBuilderTest.php
------ -----------------------------------------------------------------------
86 Drupal\Core\DependencyInjection\DependencySerializationTrait does not
support private properties.
🪪 dependencySerializationTraitProperty.unsupportedPrivateProperty
💡 See https://www.drupal.org/node/3110266
------ -----------------------------------------------------------------------
------ ---------------------------------------------------------------------
Line tests/src/Unit/Traits/NameFormSettingsHelperTraitTest.php
------ ---------------------------------------------------------------------
53 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
------ ---------------------------------------------------------------------
------ -----------------------------------------------------------------------
Line tests/src/Unit/Utility/FormattedNameTokenReplacementTest.php
------ -----------------------------------------------------------------------
465 Drupal\Core\DependencyInjection\DependencySerializationTrait does not
support private properties.
🪪 dependencySerializationTraitProperty.unsupportedPrivateProperty
💡 See https://www.drupal.org/node/3110266
465 Read-only properties are incompatible with
Drupal\Core\DependencyInjection\DependencySerializationTrait when the
trait is used by a parent class on PHP < 8.4.
🪪 dependencySerializationTraitProperty.unsupportedReadOnlyProperty
💡
Drupal\Core\DependencyInjection\DependencySerializationTrait::__wakeu
p() cannot initialize a read-only property declared in a child class.
Use the trait in this class directly, or remove the readonly
modifier.
466 Drupal\Core\DependencyInjection\DependencySerializationTrait does not
support private properties.
🪪 dependencySerializationTraitProperty.unsupportedPrivateProperty
💡 See https://www.drupal.org/node/3110266
467 Drupal\Core\DependencyInjection\DependencySerializationTrait does not
support private properties.
🪪 dependencySerializationTraitProperty.unsupportedPrivateProperty
💡 See https://www.drupal.org/node/3110266
468 Drupal\Core\DependencyInjection\DependencySerializationTrait does not
support private properties.
🪪 dependencySerializationTraitProperty.unsupportedPrivateProperty
💡 See https://www.drupal.org/node/3110266
468 Read-only properties are incompatible with
Drupal\Core\DependencyInjection\DependencySerializationTrait when the
trait is used by a parent class on PHP < 8.4.
🪪 dependencySerializationTraitProperty.unsupportedReadOnlyProperty
💡
Drupal\Core\DependencyInjection\DependencySerializationTrait::__wakeu
p() cannot initialize a read-only property declared in a child class.
Use the trait in this class directly, or remove the readonly
modifier.
------ -----------------------------------------------------------------------
------ ---------------------------------------------------------------------
Line tests/src/Unit/Utility/NameOptionValidatorTest.php
------ ---------------------------------------------------------------------
40 Storing entity storage as a class property is not recommended. Call
Drupal\Core\Entity\EntityTypeManagerInterface::getStorage() at the
call-site instead.
🪪 drupal.entityStoragePropertyAssignment
💡 See
https://mglaman.dev/blog/dependency-injection-anti-patterns-drupal
------ --------------------------------------------------------------------- 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:
Comments
Comment #3
bluegeek9 commented