{"push_id":1139757537,"size":1,"distinct_size":0,"ref":"refs/heads/master","head":"6ffb098b203a3807dc79e0776062edb08819829e","before":"0dcb06fe704ff6ea700bff4c3d5d819ba9009ef3","commits":[{"sha":"6ffb098b203a3807dc79e0776062edb08819829e","author":{"name":"Joshua Clayton","email":"5b0c9cc8624b2c5abaa68d2e94b347d96bdf7fde@gmail.com"},"message":"Initial support of aliases based on wildcard matching\n\nWhy?\n====\n\nDynamic languages, and Rails in particular, support some fun method\ncreation. One common pattern is, within RSpec, to create matchers\ndynamically based on predicate methods. Two common examples are:\n\n* `#admin?` gets converted to the matcher `#be_admin`\n* `#has_active_todos?` gets converted to the matcher `#have_active_todos`\n\nThis especially comes into play when writing page objects with predicate\nmethods.\n\nThis change introduces the concept of aliases, a way to describe the\nbefore/after for these transformations. This introduces a direct swap\nwith a wildcard value (%s), although this may change in the future to\nsupport other transformations for pluralization, camel-casing, etc.\n\nExternally, aliases are not grouped together by term; however, the\nunderlying counts are summed together, increasing the total occurrences\nand likely pushing the individual method out of \"high\" likelihood into\n\"medium\" or \"low\" likelihood.\n\nCloses #19.","distinct":false,"url":"https://api.github.com/repos/joshuaclayton/unused/commits/6ffb098b203a3807dc79e0776062edb08819829e"}]}
{"actor":{"display_login":"joshuaclayton"}}