Move hooks and emitters all to the eventdispatcher
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
We have these old hooks and eventemitters still around.
I vote to move them all to the eventdispatcher. Then we can still have the events emitted as a legacy solution for a few releases. And then kill them off. That way we'll at some point finally have 1 unified system.
CC: @ChristophWurst @nickvergessen
Migrated events
The following collection lists legacy hooks/events/emitters that continue to trigger their predecessor to keep backward compatibility. They need to be removed once the old methods are dropped:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's empty “Migrated events” section and locating the legacy hooks, event emitters, and eventdispatcher entry points in the repository. The issue does not name files, tests, or a concrete subset of events, so the scope and completion criteria need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100