Started playing around with an event listener mechanism
And I started playing around with a new feature that would be an event listener mechanism to be able to react on events when gacela resolves class names, so the user can do whatever they want: for example debugging, logging, tracing… This is the current PR with the idea so far: https://github.com/gacela-project/gacela/pull/215 in case you’re interested and/or you see some potential “waste” or “opportunity”" in such a feature 🧠
Comments
-
An event system in Gacela would be a killer feature!!
0 -
Having a 👀 at the PR now.
0 -
The question now is, what type of events would you be interested from gacela? I created so far these:
• ResolvedClassCreatedEvent
• ResolvedClassCachedEvent
• ResolvedClassTryFormParentEvent
• ResolvedDefaultClassEvent
And all these events contains theClassInfo
, so you’ll know all info about the class that it’s been resolved and how0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 896 Developer Corner
- 758 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 23 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 68 Spryker Safari Questions
- 50 Random