json-tape

json-tape

Executes a series of commands on an initial state.

npm install --save json-tape

• Faster mutation of JSON when combined with node-rapidJSON
• Delay evaluation of properties to the client side to reduce server-side load
• Use self-modifying command logs for conditionals and loops
• Easily extend the base instruction set to add your own custom commands

Quick start

json-tape can be run using the default tokenizer and instruction set to execute a series of json_asm commands.

const commandPlayer = require('json-tape')(); // <- Pass `tokenizer` or `instructionSet` as parameters to override
const state = {};
const commands = /* A string of commands */;

commandPlayer.play(commands, state, (error, result) => {
	console.log('Finished playing the command log', error, result);
});

More details

json-tape lets you apply a sequence of commands to an initial state. The format of the commands and the application of those commands to the state is customisable via the tokenizer and instructionSet parameters respectively.

We also came up with a low level method for applying operations to a JSON object which is caled json_asm which might be interesting, details are at the bottom. (Note that json-tape doesn't require that you use json_asm instruction set or the plain_text_delimiters log format—they are there as example).

Looking at an example command log (a simplification of /tests/sample_log.txt), we might have some json_asm commands to replay on the initial state.

// Commands
store:/results/0/weight:4
add:/results/0/weight:/results/0/weight:2

// Initial state
{
	results: [{ weight: 200 }, { weight: 100 }]
}

What happens when we run the default log replayer on this log?

• Our log format tokenizer (plain_text_delimiters) turns the log into command objects, i.e.

  [
  	{ op: 'store', args: ['/results/0','weight','4'] },
  	{ op: 'add', args: ['/results/0','weight','/results/0/weight', '2'] }
  ]
  

• The json-tape then plays each of these command objects on the state by calling the function matching op on the json_asm instruction set. json_asm is responsible for mutating the state and doing futher processing of the arguments to reflect the command called.

And so after running the json-tape we end up with the resulting state

// After we play each command
{
	results: [{ weight: 6 }, { weight: 100 }]
}

json_asm

json_asm is a little instruction format that allows for efficient mutation of a JSON object by specifying changes with simple commands (load, store, add, sort, etc.). It's not required to use json-tape, but it's kind of interesting.

Look at the following command specified using json_asm and the plain_text_delimiters log format

add:/results/0/weight:/results/0/weight:2

• add is the action, i.e. the opcode
• /results/0/weight is the lvalue, i.e. where we should store the result
• /results/2/weight and 2 are the operands for add. json_asm will dereference pointers
• String literal operands need to be wrapped in quotes—unquoted strings are treated as pointers