Project

General

Profile

Actions

Enhancement #141

closed

virtual attributes

Added by Marc Dequènes almost 14 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Category:
Interface :: API
Target version:
Start date:
2010-09-06
Due date:
% Done:

100%

Estimated time:
Patch Available:
No
Found in Versions:
Confirmed:
No
Branch:
Help Needed:

Description

In order to work around real attributes difficulties, obscure formats, ...
Virtual attributes accessors would get/set one or multiple real attributes in a cleaner or simpler way (can accept several kind of inputs and canonicalize for exemple).


Related issues 1 (0 open1 closed)

Related to LdapShadows - Enhancement #142: forbidden attributesResolvedMarc Dequènes2010-09-06

Actions
Actions #1

Updated by Marc Dequènes almost 14 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 40
Actions #2

Updated by Marc Dequènes almost 14 years ago

  • % Done changed from 40 to 60
What is missing:
  • search with vattrs (post-filter ?)
  • proper declaration with type handling (decorators ?)
Actions #3

Updated by Marc Dequènes over 13 years ago

Searching vattrs is quite difficult. Even if you know which kind of objects or aspects you want, still an attribute could be real in certain objects and virtual in others, so it is impossible to guess what to find if we don't show vattrs as special attributes. The only simple way i see would be to allow post-filter of any kind of attributes, using a prefix like "filter:", which would then match real and virtual attributes without having to care of their type.

Actions #4

Updated by Marc Dequènes over 13 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100
Actions

Also available in: Atom PDF