{"push_id":912637453,"size":16,"distinct_size":3,"ref":"refs/heads/cli-view-no-interleave","head":"822426f006fc7db1c43b388c17f6338e774c63a4","before":"a70d1a9806b0616cdd92a1349852bb96400171bd","commits":[{"sha":"f9ae0a72b02cf4c9800db894e2ed71fcdabb39fe","author":{"email":"28fd8c9e6b827484080d2495ad7b7a2e946b3763@jut.io","name":"Michael Demmer"},"message":"test: rework the unit tests for the parsers to be more robust\n\nUpdate the various parser tests to return a promise from each test\ncase and include the checks as part of the promise chain as opposed\nto the previous approach in which the tests would throw expectation\nerrors from within the context of the emit callback.\n\nThis should help localize failures more clearly.\n\nAs part of this change, update the tests to properly handle the case\nwhere the parser is given a limit on the number of points per emit\nso that it properly expects an empty array at the end of the test.\n\nThis was causing intermittent failures in travis.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/f9ae0a72b02cf4c9800db894e2ed71fcdabb39fe"},{"sha":"424b6310e8a2a76bd980d5a5ba4734e8751389ff","author":{"email":"649d1152bb80f39865b11b05bcf65515a12de820@jut.io","name":"Mark Stemm"},"message":"Drop the \"code \" from the error string.\n\nFor error strings like:\n\n<input>:1:17:\n   1:read from gmail -from :1 hour ago: | view table\n                     ^^^^^\nOptions must be specified before filter expressions. code (JUTTLE-SYNTAX-ERROR-WITHOUT-EXPECTED)\n\nthe \"code \" is not needed, so remove it.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/424b6310e8a2a76bd980d5a5ba4734e8751389ff"},{"sha":"1fab3ce1cddac3756836dab0b29d8df2939c9ab7","author":{"email":"28fd8c9e6b827484080d2495ad7b7a2e946b3763@jut.io","name":"Michael Demmer"},"message":"test: fix the invalid file parser tests as per PR feedback","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/1fab3ce1cddac3756836dab0b29d8df2939c9ab7"},{"sha":"ab7ce390a822edf1177af8f9fe32705b25ee1d44","author":{"email":"649d1152bb80f39865b11b05bcf65515a12de820@jut.io","name":"Mark Stemm"},"message":"Merge pull request #8 from juttle/no-code-in-error-string\n\nDrop the \"code \" from the error string.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/ab7ce390a822edf1177af8f9fe32705b25ee1d44"},{"sha":"1da999d65aec57d0c01669cd01d72ea0a0f7d1c3","author":{"email":"0d8f40f6b8e0c9f2d1afe0972711fc84bc1d6e5c@gmail.com","name":"Rodney Lopes Gomes"},"message":"Merge pull request #16 from juttle/fix-parser-tests\n\ntest: rework the unit tests for the parsers to be more robust","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/1da999d65aec57d0c01669cd01d72ea0a0f7d1c3"},{"sha":"a97e29302675738d4f02746edb58101b141f22cc","author":{"email":"4b7b5fdad9192070654df4c9088a10e7bb01991f@jut.io","name":"David Majda"},"message":"ClientSink: Remove `file` sink from comment (it no longer exists)","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/a97e29302675738d4f02746edb58101b141f22cc"},{"sha":"e72627a5974ab092085b2e6875289c4b586265a6","author":{"email":"4b7b5fdad9192070654df4c9088a10e7bb01991f@jut.io","name":"David Majda"},"message":"parser: Extract `processOptions` from `parse` and `parseSync`","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/e72627a5974ab092085b2e6875289c4b586265a6"},{"sha":"4ea94a939eaf1ddc4ea9e8e338a6f81235218058","author":{"email":"4b7b5fdad9192070654df4c9088a10e7bb01991f@jut.io","name":"David Majda"},"message":"parser: Use function statement syntax for `defaultResolver`\n\nThere is no reason to use function expression syntax which was the case\nuntil now.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/4ea94a939eaf1ddc4ea9e8e338a6f81235218058"},{"sha":"4ca0b1430505227231dabb38ec2e59ef4483779c","author":{"email":"4b7b5fdad9192070654df4c9088a10e7bb01991f@jut.io","name":"David Majda"},"message":"parser: Extract `extractImports` from `parse` and `parseSync`\n\nThis eliminates a bit of duplication.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/4ca0b1430505227231dabb38ec2e59ef4483779c"},{"sha":"34e4b8c25ce415b9fd85471843b54f9a0a50d638","author":{"email":"4b7b5fdad9192070654df4c9088a10e7bb01991f@jut.io","name":"David Majda"},"message":"parser: Also collect ASTs in `parseSync`\n\nIn `parse`, the resulting set of modules is built by collecting their\nASTs in a closure variable (`asts`). In `parseSync`, it was built\nrecursively, but a closure variable (`names`) was needed anyway to track\ncircular dependencies.\n\nThis commit changes `parseSync` to also collect module ASTs in a closure\nvariable, unifying the approaches.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/34e4b8c25ce415b9fd85471843b54f9a0a50d638"},{"sha":"19eb102a6bf8ccde239bc0be3f734552ba16b3e7","author":{"email":"4b7b5fdad9192070654df4c9088a10e7bb01991f@jut.io","name":"David Majda"},"message":"parser: Extract `buildModuleDefs` from `parse` and `parseSync`\n\nThis eliminates a bit of duplication.","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/19eb102a6bf8ccde239bc0be3f734552ba16b3e7"},{"sha":"af97ace5f1eedbd29f7dba6a1ca831e73ca1e8b4","author":{"email":"aa743a0aaec8f7d7a1f01442503957f4d7a2d634@majda.cz","name":"David Majda"},"message":"Merge pull request #19 from juttle/parser-cleanups-structural\n\nParser cleanups: Structural changes","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/af97ace5f1eedbd29f7dba6a1ca831e73ca1e8b4"},{"sha":"eb6dbc1a1c2213b2126072221dfcf935d4a46de8","author":{"email":"649d1152bb80f39865b11b05bcf65515a12de820@jut.io","name":"Mark Stemm"},"message":"Merge pull request #18 from juttle/client-sink-remove-file-from-comment\n\nClientSink: Remove `file` sink from comment (it no longer exists)","distinct":false,"url":"https://api.github.com/repos/juttle/juttle/commits/eb6dbc1a1c2213b2126072221dfcf935d4a46de8"},{"sha":"95372e05b20092cd5046946bf90df20031bef3b8","author":{"email":"28fd8c9e6b827484080d2495ad7b7a2e946b3763@jut.io","name":"Michael Demmer"},"message":"client-sink-mgr: pass the list of sinks to each view's constructor\n\nViews may want to change their behavior based on which other views\nare present in the program, so pass the full list of views into the\nconstructor when creating them.\n\nPreviously the client-sink-mgr \"env\" was passed to the constructor,\nbut none of the views used it, so that is no longer included.","distinct":true,"url":"https://api.github.com/repos/juttle/juttle/commits/95372e05b20092cd5046946bf90df20031bef3b8"},{"sha":"4e9fc39a5a5435e08924f9ece4102b424fcf0cdd","author":{"email":"28fd8c9e6b827484080d2495ad7b7a2e946b3763@jut.io","name":"Michael Demmer"},"message":"table: fix progressive mode option to have no default and be truthy\n\nNow that client-sink-mgr sets the progressive mode option, remove the\ndefault from the view itself.\n\nAlso fix a problem where the view was inconsistent in how it checked\nthe option -- in one case it was checking for \"truthiness\" while in\nthe other it was checking for explicit \"false\", which caused problems\nin the tests where the option was undefined.\n\nWhen using progressive mode with more than one view in the program,\nthe output is interleaved and becomes basically unreadable. Change\nthe initialization so that progressive mode defaults to true only\nif there is exactly one view in the program.","distinct":true,"url":"https://api.github.com/repos/juttle/juttle/commits/4e9fc39a5a5435e08924f9ece4102b424fcf0cdd"},{"sha":"822426f006fc7db1c43b388c17f6338e774c63a4","author":{"email":"28fd8c9e6b827484080d2495ad7b7a2e946b3763@jut.io","name":"Michael Demmer"},"message":"text view: add support a progressive mode option\n\nAdd a progressive mode option with the same semantics as the table\nview.","distinct":true,"url":"https://api.github.com/repos/juttle/juttle/commits/822426f006fc7db1c43b388c17f6338e774c63a4"}]}