From the beginning, the (has) section of WITCH code was supposed to reflect the current state of data in the database. At some point I confused myself thinking that scripts would be templates for new objects that could be used by multiple users and started thinking about (has) as purely default data.
This issue covers updating injecting current kv data into a WITCH script as it is requested by the client.
Since we have a locking mechanism already, I'd like to prevent kv data from being written while an object is locked for editing -- the writes can silently fail.
From the beginning, the
(has)section of WITCH code was supposed to reflect the current state of data in the database. At some point I confused myself thinking that scripts would be templates for new objects that could be used by multiple users and started thinking about(has)as purely default data.This issue covers updating injecting current kv data into a WITCH script as it is requested by the client.
Since we have a locking mechanism already, I'd like to prevent kv data from being written while an object is locked for editing -- the writes can silently fail.