Re: REST-API: Link/Multilink Properties

On Fri, Mar 22, 2019 at 02:40:53PM -0400, John P. Rouillard wrote:
> 
> Yup label property is the way to go. The proprty with the name "name"
> IIRC is a fallback for the label property if no explicit labelprop is
> set.

The labelprop defaults to the key property. The class 'status' etc all
have a key property the name of which is 'name' in most cases.
Otherwise only "title" is special: If no key prop exists and the item
has a 'title' it will be the labelprop unless explicitly set in the
schema with setlabelprop. Otherwise the alphabetically first property is
the labelprop (usually "activity"). Same for orderprop but the special
name here is "order". I know, I've implemented labelprop and orderprop a
long time ago :-)
So all classes always have a labelprop and an orderprop.

Note that a nice change to the standard schema would be to set 'date' as
the orderprop of the 'msg' class: From time to time I change a mail I've
forwarded to the tracker and edit in the original author and date. If
activity is the order prop the ordering of messages will be wrong because
the message will be ordered by last change. So in all my trackers I have
the orderprop of msg set to 'date'.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]