{"push_id":2411133527,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"fe84336e203e70799265f4864a97b37c73bf1a2c","before":"93c032b57bb864563342f8e5e10c18c7788ed697","commits":[{"sha":"1560bf92f85d48e53706cabcfd6177e42c1ee786","author":{"name":"Jason Roelofs","email":"a87a28356e60dc5290bfbdb06d93b8b39ac732bc@gmail.com"},"message":"Evaluate basic filters!\n\nThis required a couple of changes to how we're doing things. After\nputting in the pieces in the parser to get contextual nodes so we know\nwe are dealing with a filter expression, figuring out where to store\nfilters, how to access them, and how to call them became the big\nquestion. To make things easy, I'm starting with basic filters with no\nparameters.\n\nDue to the dynamic nature of Liquid, our object system needs to be just\nas dynamic. This conflicts pretty hard with Go's type system, requiring\nsome mapping and wrapping layers to let us work with a more dynamic type\nsystem on top of Go. With that mostly in place, I'm starting with\nfilters taking `object.Objects` though I'd love to play with making\nfilters straight-up go methods with types and building wrappers around\nthem for the object <-> Go types management. This will play in even\nstronger when I play with C-exports and the FFI for defining custom\nfilters.","distinct":true,"url":"https://api.github.com/repos/jasonroelofs/late/commits/1560bf92f85d48e53706cabcfd6177e42c1ee786"},{"sha":"fe84336e203e70799265f4864a97b37c73bf1a2c","author":{"name":"Jason Roelofs","email":"a87a28356e60dc5290bfbdb06d93b8b39ac732bc@gmail.com"},"message":"Add parameters to filters\n\nSeems to work. Passing all extra parameters as it's own structure into\nfilters, ensuring the syntax of a filter function stays the same.","distinct":true,"url":"https://api.github.com/repos/jasonroelofs/late/commits/fe84336e203e70799265f4864a97b37c73bf1a2c"}]}
{"actor":{"display_login":"jasonroelofs"}}