Re: REST-API: "content" Properties

Ralf Schlatterbeck <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.devel
Message-ID <[email protected]>
On Thu, Mar 21, 2019 at 11:50:41AM +0100, Ralf Schlatterbeck wrote:
> Currently the "content" property of messages and files is displayed just
> as any other normal property. Especially in the case of file
> attachments, the content can be huge, making the resulting json huge in
> turn. What do you think about replacing the content property with a link
> to the actual content (the normal download link of a file or message)
> and only adding it with a @verbose option?

I've now changed this:
I've added a @verbose parameter which controls (among others) how the
content property is displayed. With @verbose < 2 the content is
displayed as a dictionary containing a link to the download of the file
or message. With @verbose >= 2 the old behavior, displaying the content
property as a possibly very large json string is chosen.

-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.