Feature #25667

Generalise implementation of view / controller hooks for easier plugin development

Added by Stephane Evr 6 months ago. Updated 5 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Plugin API
Target version:-
Resolution:

Description

I have been developing several plugins for our Redmine, and hooks are a really good mechanism overall, but I have been struggling with the way they are partially implemented or even missing in some views / controllers.

It would be nice to have hooks implemented for all forms / controllers, equally.

Let me give some examples:

  • IssuesController has hooks for the Create action, but not for the Update action
  • IssueStatuses form partial has a call_hook, but it does not add the form itself (f) as a param, which makes it impossible to add additional elements to the form itself. The related IssueStatusesController does not have hooks for the Create or Update action
  • There are hooks for the Users form, and the form is passed as a param, which is nice, but there is no hook at all in the UsersController (Create, Update...)

History

#1 Updated by Toshi MARUYAMA 5 months ago

  • Category set to Plugin API

Also available in: Atom PDF