{"push_id":1378105660,"size":2,"distinct_size":2,"ref":"refs/heads/update-closure","head":"a378718f87828cc833c6c40a4ed5bf9c04211224","before":"0889f4c59dd4090b094cec696adba969a35519ed","commits":[{"sha":"3ccdf0f1043e53106d89d8c94489eaf5702bdb13","author":{"name":"David Purpura","email":"a9aa038d7d1d642d9f05c4e569cec139880b0be4@users.noreply.github.com"},"message":"fix: Make newline insertion more consistent. (#415)\n\nSummary:\r\nCurrently newline insertion breaks when the previous node ends with a\r\nsemi-colon, due to Closure Compiler's automatic semicolon insertion.\r\n\r\nThat is, Gents outputs:\r\n```typescript\r\nconst foo = 4\r\n  ;\r\nclass Bar{}\r\n```\r\nwhich gets formatted by clang-format to:\r\n```typescript\r\nconst foo = 4;\r\nclass Bar{}\r\n```\r\n\r\nThis PR changes the insertion logic to insert a newline before the node\r\nis written, so that it does not fall victim to semicolon insertion.","distinct":true,"url":"https://api.github.com/repos/dpurp/clutz/commits/3ccdf0f1043e53106d89d8c94489eaf5702bdb13"},{"sha":"a378718f87828cc833c6c40a4ed5bf9c04211224","author":{"name":"David Purpura","email":"c9db62eca8cb844f23acd3564c54fd8856627bdb@google.com"},"message":"chore: Update to the lastest Closure Compiler version","distinct":true,"url":"https://api.github.com/repos/dpurp/clutz/commits/a378718f87828cc833c6c40a4ed5bf9c04211224"}]}
{"actor":{"display_login":"dpurp"}}