|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Unfortunately the antipattern of Actionable returning a mutable collection from getActions, coupled with questionable and inconsistent behaviors of its subtypes, has made it seemingly impossible to compatibly change how Actionable.getActions works. The same is true of nonfinal Actionable subtypes like AbstractItem which do not themselves currently override Actionable methods.
The only compatible course is to introduce a new method which would include entries from a TransientActionFactory, though then lots of code would need to be updated to call it: basically anything which calls getActions and treats the result as read-only.
(And User and View are not Actionable despite having comparable methods and transient factories! So they cannot use any new facility.)