Mercurial > p > roundup > code
view website/issues/detectors/messagesummary.py @ 5729:9ea2ce9d10cf
A few internet references report that etags for the same underlying
resource but with different representation (xml, json ...) should have
different etags.
That is currently not the case. Added code to allow incorporation of
representation info into the etag. By default the representation is
"json", but future patches can pass the representation down and modify
flow to match requested representation.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 25 May 2019 14:23:16 -0400 |
| 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
