I’ve two modules, every of which is defining a normalizer service
module_one.providers.yml
providers: module_one.normalizer.node_entity: class: Drupalmodule_oneNormalizerModuleOneEntityNormalizer arguments: ['@entity_type.manager'] tags: - { identify: normalizer, precedence: 10 }
module_two.providers.yml
providers: module_two.normalizer.node_entity: class: Drupalmodule_twoNormalizerModuleTwoEntityNormalizer arguments: ['@entity_type.manager'] tags: - { identify: normalizer, precedence: 10 }
For every module, I’m creating a definite normalizer and presumably defining a separate namespace, ex:
<?php namespace Drupalmodule_oneNormalizer; use DrupalCoreEntityEntityTypeManagerInterface; use DrupalserializationNormalizerContentEntityNormalizer; use DrupalnodeNodeInterface; /** * Converts Drupal Development Company Drupal entity object constructions to a normalized array. */ class ModuleOneEntityNormalizer extends ContentEntityNormalizer { ...
Drupal Development Service downside is that with each modules enabled, one service is obstructing Drupal Development Company different – Drupal Development Company serializer / normalizer fires as anticipated for Drupal Development Company first one however not for Drupal Development Company second. Drupal Development Service solely strategy to get Drupal Development Company different one to be acknowledged is to extend its precedence however that blocks Drupal Development Company first.
What am I lacking in Drupal Development Company definitions that will forestall these two providers from conflicting with one another?