{"push_id":629943561,"size":6,"distinct_size":5,"ref":"refs/heads/jaro_winkler","head":"fa0cbc48a731d4bda5ea1407b13c4242c68ec6ed","before":"f9e83520b7852412e67ef9cd2a2209ec1e9610b8","commits":[{"sha":"1f7db5b0e9e6342099b2901ba30ec4f7d230277f","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@yukinishijima.net","name":"Yuki Nishijima"},"message":"Remove \"@@\" from class variable names that comes from NameError#name","distinct":false,"url":"https://api.github.com/repos/yuki24/did_you_mean/commits/1f7db5b0e9e6342099b2901ba30ec4f7d230277f"},{"sha":"818c43a6a7950341b0525f01543dc832a361d271","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@yukinishijima.net","name":"Yuki Nishijima"},"message":"Start using Jaro-Winkler distance\n\nLeveshtein distance is great, but sometimes it doesn't catch a name that\nshould be caught. For instance, when 'drag' is typed and the correct one\nis 'drag_to', did_you_mean fails to find 'drag_to'.\nWith Jaro-Winkler distance, suggestions will be more accurate.","distinct":true,"url":"https://api.github.com/repos/yuki24/did_you_mean/commits/818c43a6a7950341b0525f01543dc832a361d271"},{"sha":"b9d8abf7219e6eb424e146c746688281bcc249d7","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@yukinishijima.net","name":"Yuki Nishijima"},"message":"Tweak Jaro-winkler distance scoring\n\nThe prefix bonus actually makes suggestions less accurate. Let's use\njust Jaro distance and see if it works well. Also, change threshould\ndepending on the length of the input so it can be smarter even when\nthe input is less than 3 characters.","distinct":true,"url":"https://api.github.com/repos/yuki24/did_you_mean/commits/b9d8abf7219e6eb424e146c746688281bcc249d7"},{"sha":"426cfd4ee77ce9752de35cd726e5fd059a26e15b","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@yukinishijima.net","name":"Yuki Nishijima"},"message":"Implement jaro-winkler distance\n\nSo it doesn't have to be dependant on jaro_winkler gem.","distinct":true,"url":"https://api.github.com/repos/yuki24/did_you_mean/commits/426cfd4ee77ce9752de35cd726e5fd059a26e15b"},{"sha":"e2d47afbe0a28a0b60264a0894f5bef44f7404fe","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@yukinishijima.net","name":"Yuki Nishijima"},"message":"Make Jaro distance colculation slightly faster\n\n  Calculating -------------------------------------\n                before     3.278k i/100ms\n                 after     4.117k i/100ms\n  -------------------------------------------------\n                before     32.884k (¡Þ 6.0%) i/s -    167.178k\n                 after     41.728k (¡Þ 6.0%) i/s -    209.967k\n\n  Comparison:\n                 after:    41727.7 i/s\n                before:    32884.0 i/s - 1.27x slower","distinct":true,"url":"https://api.github.com/repos/yuki24/did_you_mean/commits/e2d47afbe0a28a0b60264a0894f5bef44f7404fe"},{"sha":"fa0cbc48a731d4bda5ea1407b13c4242c68ec6ed","author":{"email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@yukinishijima.net","name":"Yuki Nishijima"},"message":"Fix the wrong jaro-winkler alrorythm\n\nGiven we have 'does_exist' and 'doesnt_exist', The jaro_winkler gem\nreturns 0.9666... while the original implementation[1] returns 0.9066...\n\nFrom a user perspective, both of the right and wrong ones don't actually\nmeet the user satisfaction, but the right one is slightly better as\nsometimes the result would be lower than the wrong one.\n\n[1]: http://web.archive.org/web/20100227020019/http://www.census.gov/geo/msb/stand/strcmp.c","distinct":true,"url":"https://api.github.com/repos/yuki24/did_you_mean/commits/fa0cbc48a731d4bda5ea1407b13c4242c68ec6ed"}]}