#3520 closed enhancement (fixed)
ITicketChangeListener.ticket_changed should be passed the author of the change
Reported by: | Owned by: | Matthew Good | |
---|---|---|---|
Priority: | normal | Milestone: | 0.10 |
Component: | general | Version: | devel |
Severity: | normal | Keywords: | journaling |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
It is difficult or impossible to find this information otherwise.
Attachments (0)
Change History (6)
comment:1 by , 18 years ago
Keywords: | journaling added |
---|---|
Owner: | changed from | to
comment:2 by , 18 years ago
Milestone: | → 0.10 |
---|
Would be a good idea to get this change into 0.10 to avoid the API breakage in a subsequent release.
follow-up: 5 comment:3 by , 18 years ago
You mean that for 0.10, we should simply add the author info, like:
- def ticket_changed(ticket, comment, old_values): + def ticket_changed(ticket, author, comment, old_values):
Yes, why not.
But, I think that in the long run, the API should evolve anyway, along the lines of the proposal mentioned above.
comment:4 by , 18 years ago
Owner: | removed |
---|
I'll do something about this in 0.11, if in the meantime (for 0.10 or 0.10.x) someone wants to implement this, feel free.
comment:5 by , 18 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
Replying to cboos:
You mean that for 0.10, we should simply add the author info, like:
- def ticket_changed(ticket, comment, old_values): + def ticket_changed(ticket, author, comment, old_values):
Yes, why not.
For consistency with the IWikiChangeListener
maybe author
should go after comment
:
def ticket_changed(ticket, comment, author, old_value):
I can do this to make sure it gets in for 0.10.
See also TracDev/Proposals/Journaling, which discusses the matter of making the change listener interfaces more effective.