Add standard documentation for dispatched events, in the same manner traditional hooks are documented.
At first I thought the module didnt not provide any mechanism to hook, especially after searching the project for traditional hook invocations.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3063185-document-events.patch | 1.79 KB | dpi |
Comments
Comment #2
dpiComment #3
jasonawantThank you for sharing the docs! Wonder if it would be helpful to add an example of common usage, such as altering field values, such as found in #3056470: Alterations to entity reference fields are reset because ::cloneEntity() reads the reference from the original entity..
Comment #4
strozx commentedHi, I reviewed this and it does explain the usages for dispatched events. RTBC +1
Comment #5
chegor commentedRTBC +1
Comment #6
ngkoutsaik commentedI had the same problem as @dpi while working on another issue. I thought this module did not have events.
In any case, I will mark this RTBC. The documentation is on point.
Comment #7
optimusprime619 commentedThank you very much for the clear and concise documentation. One minor nitpick if I may suggest, is that if
my_module.services.ymlcode block could be updated with aservices:key at the beginning it would help make end-users' copypastefu game on point.Comment #9
colan#3: Code for that is welcome.