Paul Fitzpatrick 876a0298a2 (core) do not look at content of recent actions when loading documents ... Summary: This removes the need for any information drawn from the content of recent actions when loading a document. The undo/redo system does need some facts about recent actions up front. But that system has an important restriction: only actions a particular client is known to have generated can be undone by that client. So in this diff, as we store which client has performed an action, we also store the few pieces of metadata about that action that the undo/redo system needs: `linkId`, `otherId`, `rowIdHint`, `isUndo` fields. These are all small integers (or in one case a boolean). An existing limitation is that information about which client has performed which action is stored in memory in the worker, and not persisted anywhere. This diff does not change that limitation, meaning that undos continue to not survive a worker transition. A reasonable way to deal with that would be to back the store with redis. Test Plan: existing tests pass Reviewers: dsagal Reviewed By: dsagal Differential Revision: https://phab.getgrist.com/D3044		2021-09-29 11:27:02 -04:00
..
client	(core) do not look at content of recent actions when loading documents	2021-09-29 11:27:02 -04:00
common	(core) do not look at content of recent actions when loading documents	2021-09-29 11:27:02 -04:00
gen-server	(core) Initial webhooks implementation	2021-09-23 14:35:39 +02:00
plugin	(core) Adding traceback to trigger formulas	2021-09-27 17:12:39 +02:00
server	(core) do not look at content of recent actions when loading documents	2021-09-29 11:27:02 -04:00
tsconfig.json	(core) move home server into core	2020-07-21 20:39:10 -04:00