Wrong service url construction for open api paths with date parameters

[timayabi2020]

The API implementation class constructs a wrong service url for services with date parameters.
The date parameter is being appended as a logical operator (date==) instead of an assignment operator (date=). See below

The affected powershell commands will be failing with the following message

The service owner has described the usage of parameters as assignment operators on such paths. See below

The Url is supposed to be constructed as such

and a successful command execution will be as below image

[peombwa]

@dolauli, any updates on when the issue will be fixed? Customers are still facing the issue when using commands that accept date parameters. Is there a workaround you'd suggest?

[dolauli]

@dolauli, any updates on when the issue will be fixed? Customers are still facing the issue when using commands that accept date parameters. Is there a workaround you'd suggest?

I do not plan to fix in v3, since it seems not a common case that an API is designed like this.
The workaround should be easy, you may change the generated code with a directive as below.

- from: sourcename.cs
  where: $
  transform: $ = $.replace('old code', 'new code')

[peombwa]

Thanks for the suggestion! We went with a similar approach by using from: source-file-csharp directive. Will be issue be addressed in v4?