Tim Alby c1c23e4bee record last author id on document flush ... This is a multi-steps process: * get a update's `user_id` from the metadata * store the `user_id` (`lastUpdatedBy`) and current date (`lastUpdatedAt`) for the document in Redis on every updates * fetch `lastUpdatedAt` and `lastUpdatedBy` from Redis on document flush * send the data to web to be persisted in Mongo		2019-05-02 11:10:02 +01:00
..
helpers	record last author id on document flush	2019-05-02 11:10:02 +01:00
ApplyingUpdatesToADocTests.coffee	include a unique id in every message published to redis	2019-03-21 12:10:15 +00:00
ApplyingUpdatesToProjectStructureTests.coffee	add acceptance test for ordering of project structure changes	2018-03-15 16:27:14 +00:00
DeletingADocumentTests.coffee	Update to build 1.0.0 build scripts	2018-02-15 16:28:40 +00:00
DeletingAProjectTests.coffee	Update to build 1.0.0 build scripts	2018-02-15 16:28:40 +00:00
FlushingAProjectTests.coffee	Update to build 1.0.0 build scripts	2018-02-15 16:28:40 +00:00
FlushingDocsTests.coffee	record last author id on document flush	2019-05-02 11:10:02 +01:00
GettingADocumentTests.coffee	Update to build 1.0.0 build scripts	2018-02-15 16:28:40 +00:00
GettingProjectDocsTests.coffee	Update to build 1.0.0 build scripts	2018-02-15 16:28:40 +00:00
RangesTests.coffee	Review feedback	2019-04-16 11:05:17 +01:00
SettingADocumentTests.coffee	Update to build 1.0.0 build scripts	2018-02-15 16:28:40 +00:00