Project

General

Profile

Enhancement #141

virtual attributes

Added by Marc Dequènes about 11 years ago. Updated almost 11 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

Related to LdapShadows - Enhancement #142: forbidden attributesResolved2010-09-06

Actions

Associated revisions

Revision a8bda213 (diff)
Added by Marc Dequènes about 11 years ago

[evol] preliminary virtual attributes support (with read only attributes support, and an example vattr) (refs #141)

Revision c2c26953 (diff)
Added by Marc Dequènes about 11 years ago

[evol] virtual attributes support §2 (aspect vattrs with example) (refs #141)

Revision 449a85cf (diff)
Added by Marc Dequènes about 11 years ago

[evol] virtual attributes support §3 (TextUI can fetch specific vattr) (refs #141)

Revision 5f929912 (diff)
Added by Marc Dequènes almost 11 years ago

[evol] vattrs: normalize when setting field with helpers (refs #141)

Revision 3f984668 (diff)
Added by Marc Dequènes almost 11 years ago

[evol] implemented vattrs search via post-filters (closes #141)

History

#1

Updated by Marc Dequènes about 11 years ago

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

Updated by Marc Dequènes about 11 years ago

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

Updated by Marc Dequènes almost 11 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.

#4

Updated by Marc Dequènes almost 11 years ago

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

Also available in: Atom PDF