Mercurial > p > roundup > code
view website/issues/detectors/messagesummary.py @ 6311:be8d5a8e090a
Fix uncaught error when parsing rest headers, document
Started this work as better docs for rest response format. But I found
406 error response was not being tested. Also there was no error for
bad Content-Type.
In rest.py fix uncaught exceptions due to invalid Accept or
Content-Type headers. If Content-type is valid but not
application/json return code 415.
Document use of accept header (was only shown in examples) and support
for q parameter. Describe using .xml and .json extensions to select
return format for testing from browser (where setting accept header is
a problem). Document 406 error code return. Document 415 error code
return and acceptable content types. Previously only doc was in
examples.
Set up tests for 406 and 415 error codes.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Fri, 01 Jan 2021 14:14:34 -0500 |
| parents | 0942fe89e82e |
| children |
line wrap: on
line source
from roundup.mailgw import parseContent def summarygenerator(db, cl, nodeid, newvalues): ''' If the message doesn't have a summary, make one for it. ''' if 'summary' in newvalues or 'content' not in newvalues: return summary, content = parseContent(newvalues['content'], config=db.config) newvalues['summary'] = summary def init(db): # fire before changes are made db.msg.audit('create', summarygenerator) # vim: set filetype=python ts=4 sw=4 et si #SHA: 538f90cb7f4eb63f77eca252b87afbe037d29c48
