json-patch | Go library to apply RFC6902 patches | JSON Processing library

RestSharp working code - as per input from Alexey Zimarev

There's already UseHttpMethodOverride baked into ASP.NET Core, and though it doesn't quite work exactly how you want it to, you could use the corresponding middleware's code as a basis for your own middleware.

Alternatively, you could write it as an anonymous method in your startup's Configure method:

Your XML is slightly off, that's what's causing the issue. There are two small issues I saw that when corrected, allow the steps to properly be interpreted by the work item:

1. should be LOWERCASE
2. Your step Ids start at 2 instead of 1

Try this XML:

Input step 1Expectation step 1 Input step 2Expectation step 2

observe and responseType are string unions, so you need to mark them as const in your options object, otherwise Typescript will infer them as type string.

Is there a special way to do this?

I am afraid there is no such way to do this.

That is because the workitem that is already in the Removed state cannot be converted to other states except New.

You could check the document Agile workflow states for some more details.

In addition, when we have chosen to Remove a certain workitem, it means that we have abandoned the workitem. If the workitem is re-enabled, it should return to the state of New.

A couple of things. First, I would suggest creating a separate web service to host your OData endpoints. Second, prior to .net 6, it's somewhat difficult to get OData and Swagger to work together. Even in .net 6, there are a few things missing when it comes to swagger.

I have an open-source project that fills in the gaps. Here's a sample project that illustrates how to use it.

https://github.com/ikemtz/NRSRx/tree/master/samples/IkeMtz.Samples.OData

After a lot of tries and errors, I found the solution below.

A solution like this is used in Patroni (but there is written in Python) where the Service has one Endpoint that always references the master node. When a failover o switchover occurs the Patroni code update the Service Endpoint. A code like this can be used whenever you have a StatefulSet and you always want to have the Service reference the master node even in a failover scenario.

Sorry, it was a basic coding / fencepost-ish error:

Indeed you have a clash in RestEasy (transitive) dependencies in your project: