Feature/fix id in route attribute

[TomaszCzyz]

When I was playing around with the client, I noticed a silly mistake in a RouteAttribute with id path parameter.
The correct format for a route is [Route("/{id}")] (the previous version was not catching the parameter [Route("/:id")]).

Another option would be to merge the GetAll and Get methods by applying the ? syntax for optional parameters.

[HttpGet]  
[Route("/")]  
[Route("/{id?}")]  
public Task<List<WeatherForecast>> GetAll(string? id, CancellationToken cancellationToken)
{
	// ...
}

However, for the sake of a clearer example, I would not do that :)

[Odonno]

Hi @TomaszCzyz

Oh yes, you are right. My bad. Can you also update the readme file? There is an example code that displays this Controller.

And I would like to stick with 2 separate endpoints for GetAll and GetById. Like you said, it is clearer that way.

[TomaszCzyz]

Hi @Odonno README updated 😉

[Odonno]

Nice. Looks good to me.

[TomaszCzyz]

Hi @Odonno, should I mention someone or can you approve the workflow to merge the PR?

[Odonno]

@kearfy is your hero.