You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we're getting close to a structured format for the packet documentation (see artemis-nerds/protocol-docs#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.
The text was updated successfully, but these errors were encountered:
Now that we're getting close to a structured format for the packet documentation (see artemis-nerds/protocol-docs#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.
The text was updated successfully, but these errors were encountered: