Enable autoconfiguration

Created on 5 March 2025, about 1 month ago

Problem/Motivation

When having hundreds of hook-containing services outside of Hooks, the 'hooks' tag is annoying, given that it can be autoconfigured.

Proposed resolution

Enable autoconfiguration.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

1.8

Component

Code

Created by

🇩🇪Germany geek-merlin Freiburg, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @geek-merlin
  • Merge request !43Enable autoconfiguration #3511292 → (Open) created by geek-merlin
  • Pipeline finished with Success
    about 1 month ago
    Total: 177s
    #441414
  • 🇩🇪Germany geek-merlin Freiburg, Germany

    This does the trick for me. Tested on a site with hundreds of autoconfigured hook services. Also fixes the related issue.

  • 🇦🇺Australia dpi Perth, Australia

    I'd like to understand the pain point a little better. Why not use put things in Hooks/ namespace and let it all get registered for you? That way you don't need to put anything in any services file?

    Is there a particular reason why that doesnt work for you? Are you using services.yml for some reason?

    Manually tagging services and adding to the yml files is something I consider to be a very rare occurrence, not business-as-usual.

  • 🇦🇺Australia dpi Perth, Australia
Production build 0.71.5 2024