[Tickets #11124] Re: decode_attribute hook an exceptions

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/11124
------------------------------------------------------------------------------
  Ticket           | 11124
  Aktualisiert Von | kd at tu-cottbus.de
  Zusammenfassung  | decode_attribute hook an exceptions
  Warteschlange    | Turba
  Version          | 3.0.12
  Typ              | Enhancement
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


kd at tu-cottbus.de (2012-04-03 20:07) hat geschrieben:


> This is debatable, but I don't see a reason to artificially limit  
> which fields we allow to pass through the hook, just for code-flow  
> reasons.
>
A composite field is defined in terms of "turba-attributes" (left-hand  
side of the map),
this is different from directly  to "backend attributes" mapped  
"turba-attributes".
What is passed to the hook as the value of a composite field?
I can't imagine a situation, where a composite field *and* a hook for  
that field makes sense.
I'd always use a direct mapping and do the other work in the hook.
Isn't a composite field not some kind of simple inline hook?

> Well, maybe we could return an array in Turba 4 instead, with a  
> boolean as the first element, whether the hook has been called.
Is it possible to do it the old-fashioned way,  pass the value by  
reference, and return a
status code?