Now that we're getting close to a structured format for the packet documentation (see https://github.com/artemis-nerds/protocol-docs/issues/50), we should look at either generating parts of this library from that, or having the parser consume that file and use it to parse packets.
We probably don't want to actually begin implementing this yet as the format will probably change in places, but we do need to decide how we're gonna use this file.
In my opinion, since we already have a gobble task that compiles ES6 -> ES5, the easiest way to go would be adding a step here that pulls the Isolinear Chips files and generates some JS files from them before compiling the ES6.
Now that we're getting close to a structured format for the packet documentation (see https://github.com/artemis-nerds/protocol-docs/issues/50), we should look at either generating parts of this library from that, or having the parser consume that file and use it to parse packets.
We probably don't want to actually begin implementing this yet as the format will probably change in places, but we do need to decide how we're gonna use this file.
In my opinion, since we already have a gobble task that compiles ES6 -> ES5, the easiest way to go would be adding a step here that pulls the Isolinear Chips files and generates some JS files from them before compiling the ES6.