a prefix for metadata in the manifest
[?]
Jan 3, 2023, 2:21 AM
CYEH4AXBCTDLTBMWC3THTJHT6KBRNSGQBFQPWTEYRRM3LI2XGKRQCDependencies
- [2]
6K5PFF6Xhelper: trimming whitespace from strings - [3]
5OVKHVY6nice way to make on.* handlers more discoverable - [4]
QFURHRTPrename globals to have a single uppercase letter - [5]
LRDM35CEapp running again - [6]
WNHI74P7load manifest in correct order - [*]
BULPIBEGbeginnings of a module for the text editor - [*]
PLKNHYZ4extract a function
Change contents
- edit in text.lua at line 933[2.172][9.438]
endfunction starts_with(s, prefix)if #s < #prefix thenreturn falseendfor i=1,#prefix doif s:sub(i,i) ~= prefix:sub(i,i) thenreturn falseendendreturn true - replacement in live.lua at line 124
if k ~= 'parent' then-- Most keys in the manifest are definitions. If we need to store any-- metadata we'll do it in keys starting with a specific prefix.if not starts_with(k, 'fw_') then - edit in live.lua at line 139
PARENT = 'fw_parent' - replacement in live.lua at line 226
Live.manifest.parent = Live.headLive.manifest[PARENT] = Live.head - replacement in live.lua at line 242
Live.manifest.parent = Live.headLive.manifest[PARENT] = Live.head - replacement in live.lua at line 251
Live.head = Live.manifest.parentLive.head = Live.manifest[PARENT] - replacement in 0001-manifest at line 1
{"parent":0,"on":1}[3.593]{"fw_parent":0,"on":1}