Seth Kinast
Seth Kinast
I saw behavior where every time I called update from the MQTT example, I always got "heatpump: update() failed". Looking at the code for update: ``` createPacket(packet, wantedSettings); writePacket(packet, PACKET_LEN);...
Currently we strictly read one packet each time `sync()` is called. This means that if `writePacket()` is ever called twice in a row before reading, a packet will be permanently...
Select states are so brittle currently. Now that we have context options (linkedin/dustjs#641) we can store the select state completely off the context stack, and rely on an ID lookup...
Will improve build speed too
Dust 2.8
Tracking issue for the 2.8 release. The goal of 2.8 is to wrap up the commits that have landed over the last year before work on a Dust 3.0. -...
( instead of pushing our own copies onto the stack ) I think anything that manually manipulates the stack directly is a smell. We already have these properties available as...
Dust 3.0
Tracking issue for Dust@3 - [ ] Remove the .join() "optimization" - [ ] Flip the default whitespace flag to not strip - [ ] ES6 modules for compiler and...
@jimmyhchan talked about this last year and I think it finally clicked for me. `dust.render` returns undefined right now and uses a callback. Jimmy talked about "streaming into templates" last...
We need tables of params. Examples of calling functions. Better descriptions.
When --split is turned on, templates are compiled in place. It would be useful to create a separate identical directory structure. For example, if templates are located at: ``` templates/foo.dust...