No route was found matching the URL and request method

[angelxmoreno]

object(GuzzleHttp\Exception\ClientException) id:0 {
protected message => 'Client error: `GET https://angelm106.sg-host.com/wp-json/wp/v2/postsper_page=10` resulted in a `404 Not Found` response:
{"code":"rest_no_route","message":"No route was found matching the URL and request method.","data":{"status":404}}
'
protected code => (int) 404
protected file => '/Users/amoreno/Projects/MetaSuggestionsApi/meta-suggestions-api/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php'
protected line => (int) 113
}

[angelxmoreno]

https://github.com/angelxmoreno/WPRestClient/blob/main/src/Core/ApiClient.php#L80

$url .= http_build_query($data);

should be

$url .= '?' . http_build_query($data);

This bug begs the question: "How was this not caught by the unit tests?"

The answer is that the HTTPClient is stubbed. Perhaps verifying the data received by the stub would have caught this.