Active
Project:
Entity Operations
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2013 at 14:49 UTC
Updated:
5 Feb 2013 at 16:52 UTC
When an entity type declares that it makes use of an operation, it does this:
'view' => array(
'handler' => 'EntityOperationsOperationEntityViewOperations',
'default' => TRUE,
),
This array is called the operation info.
But an operation handler class gets to define essential info about how its operation behaves:
function operationInfo() {
return array(
// Default behaviour is to provide a menu item.
'provides menu' => TRUE,
'uses form' => FALSE,
'provides vbo' => FALSE,
'provides views field' => TRUE,
);
}
this is called... the operation info.
And there are plenty of circumstances where we have both in play :(
This needs cleaning up -- I need to come up with a 2nd name and then use it consistently!
Comments
Comment #1
joachim commentedSo the problem with coming up with two distinct names like 'info' and 'definition' (which is what I use in one place at least) is that neither of them convey information about WHICH of the two things they refer to.
Hence I reckon at least one of them needs to say where it comes from, eg:
- operation handler info
- operation definition