{"push_id":784583157,"size":2,"distinct_size":0,"ref":"refs/heads/deployed-to-preview","head":"50f09e2863bcca1ef76bc8075ad994f209f2e49a","before":"b5976b4f42cc0fc483238091f48f3fde706f882f","commits":[{"sha":"c35c2b1940bb16b1f741ef667a9d4bf2d03da900","author":{"email":"be8758dc4a66004612e74b567a662d4f1fbf4c2e@gmail.com","name":"tijmen"},"message":"Only check spelling when explicitly requested\n\nWe currently do spelling corrections for all search requests, even when\nthe client hasn't asked for it and won't use it. Since the suggester\nmakes a separate HTTP query to elasticsearch this has significant\noverhead.\n\nWe've previously introduced the `suggest=spelling` parameter\n(https://github.com/alphagov/rummager/pull/511) and updated the sole\nuser of the feature, frontend, to send that parameter\n(https://github.com/alphagov/frontend/pull/880).\n\nWe can now restrict suggesting to clients that request it.\n\nThere are no new tests because the behaviour hasn't changed - the\nexisting acceptance test already has the `suggest=spelling` parameter,\nso it will keep working. I've resisted the urge to test the negative\ncase, because that feels like overkill (testing the absence of things\nnot asked seems potentially endless) - but I'm open to people's\nthoughts on the matter.","distinct":false,"url":"https://api.github.com/repos/alphagov/rummager/commits/c35c2b1940bb16b1f741ef667a9d4bf2d03da900"},{"sha":"50f09e2863bcca1ef76bc8075ad994f209f2e49a","author":{"email":"60c6d277a8bd81de7fdde19201bf9c58a3df08f4@tomlins.org.uk","name":"Alex Tomlins"},"message":"Merge pull request #515 from alphagov/only-add-highlighting-when-requested\n\nOnly check spelling when explicitly requested","distinct":false,"url":"https://api.github.com/repos/alphagov/rummager/commits/50f09e2863bcca1ef76bc8075ad994f209f2e49a"}]}