pokemon-showdown-client/test/parse
Guangcong Luo 2471482fb4 Battle.lineParse -> BattleTextParser.parseLine
BattleTextParser.parseLine -> BattleTextParser.parseArgs

This makes it so Battle depends on BattleTextParser, rather than
BattleTextParser depending on Battle.

This is probably better, because someone is way more likely to want
BattleTextParser standalone, than to want Battle standalone.

...which I'm sure matters to literally no one but me, but whatever. I
think it makes more sense this way.
2019-01-05 05:41:05 -06:00

24 lines
551 B
JavaScript
Executable File

#!/usr/bin/env node
const fs = require('fs');
const path = require('path');
process.chdir(path.resolve(__dirname, '..'));
require(`../js/battle-dex.js`); // only needed for toId
global.BattleText = require(`../data/text.js`).BattleText;
require(`../js/battle-text-parser.js`);
const parser = new BattleTextParser();
const readline = require('readline');
const rl = readline.createInterface({
input: process.stdin,
output: process.stdout,
terminal: false
});
rl.on('line', line => {
process.stdout.write(parser.extractMessage(line));
});