Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-21349

Impossible to register one slot for multiple signals

    XMLWordPrintable

Details

    Description

      Follow up of EZP-20069.

      It's not possible to register only one service as a slot for a selection of services (not all).

      Following configuration should work but currently only the first tag is taken into account:

      services:
          my_signal_slot:
              class: my\SignalSlotBundle\Slot\OnContentServiceSignalSlot
              arguments: [ @ezpublish.api.service.content ]
              tags:
                  - { name: ezpublish.api.slot, signal: ContentService\CreateContentDraftSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\AddRelationSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\AddTranslationInfoSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\CopyContentSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\CreateContentSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\DeleteContentSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\DeleteRelationSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\DeleteVersionSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\PublishVersionSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\TranslateVersionSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\UpdateContentMetadataSignal }
                  - { name: ezpublish.api.slot, signal: ContentService\UpdateContentSignal }
      

      Note that other compiler passes probably have the same issue.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jerome.vieilledent-obsolete@ez.no Jérôme Vieilledent (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours, 15 minutes
                2h 15m