[FromBody]JsonPatchDocument<Company><\/code> and not [FromBody]Company as we did with the PUT requests.
\n\u90e8\u5206\u66f4\u65b0\u5e76\u4e0d\u662f PATCH \u548c PUT \u4e4b\u95f4\u7684\u552f\u4e00\u533a\u522b\u3002\u8bf7\u6c42\u6b63\u6587\u4e5f\u4e0d\u540c\u3002\u4f8b\u5982\uff0c\u5bf9\u4e8e Company PATCH \u8bf7\u6c42\uff0c\u6211\u4eec\u5e94\u8be5\u4f7f\u7528 [FromBody]JsonPatchDocument<Company><\/code>\uff0c\u800c\u4e0d\u662f [FromBody]Company\uff0c\u5c31\u50cf\u6211\u4eec\u5bf9 PUT \u8bf7\u6c42\u6240\u505a\u7684\u90a3\u6837\u3002<\/p>\nAdditionally, for the PUT request\u2019s media type, we have used application\/json \u2014 but for the PATCH request\u2019s media type, we should use application\/json-patch+json. Even though the first one would be accepted in ASP.NET Core for the PATCH request, the recommendation by REST standards is to use the second one.
\n\u6b64\u5916\uff0c\u5bf9\u4e8e PUT \u8bf7\u6c42\u7684\u5a92\u4f53\u7c7b\u578b\uff0c\u6211\u4eec\u4f7f\u7528\u4e86 application\/json\uff0c\u4f46\u5bf9\u4e8e PATCH \u8bf7\u6c42\u7684\u5a92\u4f53\u7c7b\u578b\uff0c\u6211\u4eec\u5e94\u8be5\u4f7f\u7528 application\/json-patch+json\u3002\u5c3d\u7ba1 PATCH \u8bf7\u6c42\u7684 ASP.NET Core \u4f1a\u63a5\u53d7\u7b2c\u4e00\u4e2a\u9009\u9879\uff0c\u4f46 REST \u6807\u51c6\u5efa\u8bae\u4f7f\u7528\u7b2c\u4e8c\u4e2a\u9009\u9879\u3002<\/p>\n
Let\u2019s see what the PATCH request body looks like:
\n\u8ba9\u6211\u4eec\u770b\u770b PATCH \u8bf7\u6c42\u6b63\u6587\u662f\u4ec0\u4e48\u6837\u5b50\u7684\uff1a<\/p>\n
[ { "op": "replace", "path": "\/name", "value": "new name" }, { "op": "remove", "path": "\/name" } ]<\/code><\/pre>\nThe square brackets represent an array of operations. Every operation is placed between curly brackets. So, in this specific example, we have two operations: Replace and Remove represented by the op property. The path property represents the object\u2019s property that we want to modify and the value property represents a new value.
\n\u65b9\u62ec\u53f7\u8868\u793a\u4e00\u7ec4\u4f5c\u3002\u6bcf\u4e2a\u4f5c\u90fd\u653e\u5728\u5927\u62ec\u53f7\u4e4b\u95f4\u3002\u56e0\u6b64\uff0c\u5728\u8fd9\u4e2a\u7279\u5b9a\u793a\u4f8b\u4e2d\uff0c\u6211\u4eec\u6709\u4e24\u4e2a\u4f5c\uff1a\u7531 op \u5c5e\u6027\u8868\u793a\u7684 Replace \u548c Remove\u3002path \u5c5e\u6027\u8868\u793a\u6211\u4eec\u8981\u4fee\u6539\u7684\u5bf9\u8c61\u5c5e\u6027\uff0cvalue \u5c5e\u6027\u8868\u793a\u65b0\u503c\u3002<\/p>\n
In this specific example, for the first operation, we replace the value of the name property with a new name. In the second example, we remove the name property, thus setting its value to default.
\n\u5728\u8fd9\u4e2a\u7279\u5b9a\u793a\u4f8b\u4e2d\uff0c\u5bf9\u4e8e\u7b2c\u4e00\u4e2a\u4f5c\uff0c\u6211\u4eec\u5c06 name \u5c5e\u6027\u7684\u503c\u66ff\u6362\u4e3a\u65b0\u540d\u79f0\u3002\u5728\u7b2c\u4e8c\u4e2a\u793a\u4f8b\u4e2d\uff0c\u6211\u4eec\u5220\u9664\u4e86 name \u5c5e\u6027\uff0c\u4ece\u800c\u5c06\u5176\u503c\u8bbe\u7f6e\u4e3a default\u3002<\/p>\n
There are six different operations for a PATCH request:
\nPATCH \u8bf7\u6c42\u6709 6 \u79cd\u4e0d\u540c\u7684\u64cd\u4f5c\u4f5c\uff1a<\/p>\n
\n\n\nOPERATION<\/th>\n REQUEST BODY<\/th>\n EXPLANATION<\/th>\n<\/tr>\n<\/thead>\n \n\nAdd<\/td>\n { "op": "add", "path": "\/name", "value": "new value" }<\/td>\n Assigns a new value to a required property.<\/td>\n<\/tr>\n \nRemove<\/td>\n { "op": "remove","path": "\/name"}<\/td>\n Sets a default value to a required property.<\/td>\n<\/tr>\n \nReplace<\/td>\n { "op": "replace", "path": "\/name", "value": "new value" }<\/td>\n Replaces a value of a required property to a new value.<\/td>\n<\/tr>\n \nCopy<\/td>\n {"op": "copy","from": "\/name","path": "\/title"}<\/td>\n Copies the value from a property in the \u201cfrom\u201d part to the property in the \u201cpath\u201d part.<\/td>\n<\/tr>\n \nMove<\/td>\n { "op": "move", "from": "\/name", "path": "\/title" }<\/td>\n Moves the value from a property in the \u201cfrom\u201d part to a property in the \u201cpath\u201d part.<\/td>\n<\/tr>\n \nTest<\/td>\n {"op": "test","path": "\/name","value": "new value"}<\/td>\n Tests if a property has a specified value.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nAfter all this theory, we are ready to dive into the coding part.
\n\u5728\u6240\u6709\u8fd9\u4e9b\u7406\u8bba\u4e4b\u540e\uff0c\u6211\u4eec\u51c6\u5907\u6df1\u5165\u7814\u7a76\u7f16\u7801\u90e8\u5206\u3002<\/p>\n
12.1 Applying PATCH to the Employee Entity<\/h2>\n
12.1 \u5c06 PATCH \u5e94\u7528\u4e8e Employee \u5b9e\u4f53<\/p>\n
Before we start with the code modification, we have to install two required libraries:\u200c
\n\u5728\u6211\u4eec\u5f00\u59cb\u4fee\u6539\u4ee3\u7801\u4e4b\u524d\uff0c\u6211\u4eec\u5fc5\u987b\u5b89\u88c5\u4e24\u4e2a\u5fc5\u9700\u7684\u5e93\uff1a<\/p>\n
\u2022 The Microsoft.AspNetCore.JsonPatch library, in the Presentation project, to support the usage of JsonPatchDocument in our controller and
\nPresentation\u9879\u76ee\u4e2d\u7684 Microsoft.AspNetCore.JsonPatch \u5e93\uff0c\u7528\u4e8e\u652f\u6301\u5728\u63a7\u5236\u5668\u4e2d\u4f7f\u7528 JsonPatchDocument \u548c<\/p>\n
\u2022 The Microsoft.AspNetCore.Mvc.NewtonsoftJson library, in the main project, to support request body conversion to a PatchDocument once we send our request.
\n\u4e3b\u9879\u76ee\u4e2d\u7684 Microsoft.AspNetCore.Mvc.NewtonsoftJson \u5e93\uff0c\u7528\u4e8e\u652f\u6301\u5728\u53d1\u9001\u8bf7\u6c42\u540e\u5c06\u8bf7\u6c42\u6b63\u6587\u8f6c\u6362\u4e3a PatchDocument\u3002<\/p>\n
As you can see, we are still using the NewtonsoftJson library to support the PatchDocument conversion. The official statement from Microsoft is that they are not going to replace it with System.Text.Json: \u201cThe main reason is that this will require a huge investment from us, with not a very high value-add for the majority of our customers.\u201d.
\n\u5982\u60a8\u6240\u89c1\uff0c\u6211\u4eec\u4ecd\u5728\u4f7f\u7528 NewtonsoftJson \u5e93\u6765\u652f\u6301 PatchDocument \u8f6c\u6362\u3002Microsoft \u7684\u5b98\u65b9\u58f0\u660e\u662f\uff0c\u4ed6\u4eec\u4e0d\u4f1a\u7528 System.Text.Json \u66ff\u6362\u5b83\uff1a\u201c\u4e3b\u8981\u539f\u56e0\u662f\u8fd9\u9700\u8981\u6211\u4eec\u8fdb\u884c\u5927\u91cf\u6295\u8d44\uff0c\u5bf9\u4e8e\u6211\u4eec\u7684\u5927\u591a\u6570\u5ba2\u6237\u6765\u8bf4\uff0c\u9644\u52a0\u503c\u4e0d\u662f\u5f88\u9ad8\u3002<\/p>\n
By using AddNewtonsoftJson, we are replacing the System.Text.Json formatters for all JSON content. We don\u2019t want to do that so, we are going ton add a simple workaround in the Program class:
\n\u901a\u8fc7\u4f7f\u7528 AddNewtonsoftJson\uff0c\u6211\u4eec\u5c06\u66ff\u6362\u6240\u6709 JSON \u5185\u5bb9\u7684 System.Text.Json \u683c\u5f0f\u5316\u7a0b\u5e8f\u3002\u6211\u4eec\u4e0d\u60f3\u8fd9\u6837\u505a\uff0c\u56e0\u6b64\uff0c\u6211\u4eec\u5c06\u5728 Program \u7c7b\u4e2d\u6dfb\u52a0\u4e00\u4e2a\u7b80\u5355\u7684\u89e3\u51b3\u65b9\u6cd5\uff1a<\/p>\n
NewtonsoftJsonPatchInputFormatter GetJsonPatchInputFormatter() => \n new ServiceCollection()\n .AddLogging()\n .AddMvc()\n .AddNewtonsoftJson()\n .Services.BuildServiceProvider()\n .GetRequiredService<IOptions<MvcOptions>>()\n .Value.InputFormatters.OfType<NewtonsoftJsonPatchInputFormatter>()\n .First();<\/code><\/pre>\nBy adding a method like this in the Program class, we are creating a local function. This function configures support for JSON Patch using Newtonsoft.Json while leaving the other formatters unchanged.
\n\u901a\u8fc7\u5728 Program \u7c7b\u4e2d\u6dfb\u52a0\u8fd9\u6837\u7684\u65b9\u6cd5\uff0c\u6211\u4eec\u6b63\u5728\u521b\u5efa\u4e00\u4e2a\u672c\u5730\u51fd\u6570\u3002\u6b64\u51fd\u6570\u4f7f\u7528 Newtonsoft.Json \u914d\u7f6e\u5bf9 JSON Patch \u7684\u652f\u6301\uff0c\u540c\u65f6\u4fdd\u6301\u5176\u4ed6\u683c\u5f0f\u5316\u7a0b\u5e8f\u4e0d\u53d8\u3002<\/p>\n
For this to work, we have to include two more namespaces in the class:
\n\u4e3a\u6b64\uff0c\u6211\u4eec\u5fc5\u987b\u5728 class \u4e2d\u518d\u5305\u542b\u4e24\u4e2a\u547d\u540d\u7a7a\u95f4\uff1a<\/p>\n
using Microsoft.AspNetCore.Mvc.Formatters; \nusing Microsoft.Extensions.Options;<\/code><\/pre>\nAfter that, we have to modify the AddControllers method:
\n\u4e4b\u540e\uff0c\u6211\u4eec\u5fc5\u987b\u4fee\u6539 AddControllers \u65b9\u6cd5\uff1a<\/p>\n
builder.Services.AddControllers(config => { \n config.RespectBrowserAcceptHeader = true; \n config.ReturnHttpNotAcceptable = true; \n config.InputFormatters.Insert(0, GetJsonPatchInputFormatter()); \n}).AddXmlDataContractSerializerFormatters()\n.AddCustomCSVFormatter()\n.AddApplicationPart(typeof(CompanyEmployees.Presentation.AssemblyReference)\n.Assembly);\n\n\/\/ config.InputFormatters.Insert(0, GetJsonPatchInputFormatter());<\/code><\/pre>\nWe are placing our JsonPatchInputFormatter at the index 0 in the InputFormatters list.
\n\u6211\u4eec\u5c06 JsonPatchInputFormatter \u653e\u5728 InputFormatters \u5217\u8868\u4e2d\u7684\u7d22\u5f15 0 \u5904\u3002<\/p>\n
We will require a mapping from the Employee type to the EmployeeForUpdateDto type. Therefore, we have to create a mapping rule for that.
\n\u6211\u4eec\u9700\u8981\u4ece Employee \u7c7b\u578b\u5230 EmployeeForUpdateDto \u7c7b\u578b\u7684\u6620\u5c04\u3002\u56e0\u6b64\uff0c\u6211\u4eec\u5fc5\u987b\u4e3a\u6b64\u521b\u5efa\u4e00\u4e2a\u6620\u5c04\u89c4\u5219\u3002<\/p>\n
If we take a look at the MappingProfile class, we will see that we have a mapping from the EmployeeForUpdateDto to the Employee type:
\n\u5982\u679c\u6211\u4eec\u770b\u4e00\u4e0b MappingProfile \u7c7b\uff0c\u6211\u4eec\u5c06\u770b\u5230\u6211\u4eec\u6709\u4e00\u4e2a\u4ece EmployeeForUpdateDto \u5230 Employee \u7c7b\u578b\u7684\u6620\u5c04\uff1a<\/p>\n
CreateMap<EmployeeForUpdateDto, Employee>();<\/code><\/pre>\nBut we need it another way. To do so, we are not going to create an additional rule; we can just use the ReverseMap method to help us in the process:
\n\u4f46\u6211\u4eec\u9700\u8981\u53e6\u4e00\u79cd\u65b9\u5f0f\u3002\u4e3a\u6b64\uff0c\u6211\u4eec\u4e0d\u4f1a\u521b\u5efa\u5176\u4ed6\u89c4\u5219;\u6211\u4eec\u53ef\u4ee5\u4f7f\u7528 ReverseMap \u65b9\u6cd5\u6765\u5728\u6b64\u8fc7\u7a0b\u4e2d\u5e2e\u52a9\u6211\u4eec\uff1a<\/p>\n
CreateMap<EmployeeForUpdateDto, Employee>().ReverseMap();<\/code><\/pre>\nThe ReverseMap method is also going to configure this rule to execute reverse mapping if we ask for it.
\nReverseMap \u65b9\u6cd5\u8fd8\u5c06\u914d\u7f6e\u6b64\u89c4\u5219\uff0c\u4ee5\u4fbf\u5728\u6211\u4eec\u8981\u6c42\u65f6\u6267\u884c\u53cd\u5411\u6620\u5c04\u3002<\/p>\n
After that, we are going to add two new method contracts to the IEmployeeService interface:
\n\u4e4b\u540e\uff0c\u6211\u4eec\u5c06\u5411 IEmployeeService \u63a5\u53e3\u6dfb\u52a0\u4e24\u4e2a\u65b0\u7684\u65b9\u6cd5\u534f\u5b9a\uff1a<\/p>\n
using Entities.Models;\nusing Shared.DataTransferObjects;\n\nnamespace Service.Contracts\n{\n public interface IEmployeeService\n {\n IEnumerable<EmployeeDto> GetEmployees(Guid companyId, bool trackChanges);\n EmployeeDto GetEmployee(Guid companyId, Guid id, bool trackChanges);\n EmployeeDto CreateEmployeeForCompany(Guid companyId, EmployeeForCreationDto employeeForCreation, bool trackChanges);\n void DeleteEmployeeForCompany(Guid companyId, Guid id, bool trackChanges);\n void UpdateEmployeeForCompany(Guid companyId, Guid id, EmployeeForUpdateDto employeeForUpdate, bool compTrackChanges, bool empTrackChanges);\n (EmployeeForUpdateDto employeeToPatch, Employee employeeEntity) GetEmployeeForPatch(Guid companyId, Guid id, bool compTrackChanges, bool empTrackChanges); \n void SaveChangesForPatch(EmployeeForUpdateDto employeeToPatch, Employee employeeEntity);\n }\n}<\/code><\/pre>\nOf course, for this to work, we have to add the reference to the Entities project.
\n\u5f53\u7136\uff0c\u8981\u4f7f\u5176\u6b63\u5e38\u5de5\u4f5c\uff0c\u6211\u4eec\u5fc5\u987b\u6dfb\u52a0\u5bf9 Entities \u9879\u76ee\u7684\u5f15\u7528\u3002<\/p>\n
Then, we have to implement these two methods in the EmployeeService class:
\n\u7136\u540e\uff0c\u6211\u4eec\u5fc5\u987b\u5728 EmployeeService \u7c7b\u4e2d\u5b9e\u73b0\u8fd9\u4e24\u4e2a\u65b9\u6cd5\uff1a<\/p>\n
public (EmployeeForUpdateDto employeeToPatch, Employee employeeEntity) GetEmployeeForPatch(Guid companyId, Guid id, bool compTrackChanges, bool empTrackChanges)\n{\n var company = _repository.Company.GetCompany(companyId, compTrackChanges);\n if (company is null)\n throw new CompanyNotFoundException(companyId);\n var employeeEntity = _repository.Employee.GetEmployee(companyId, id, empTrackChanges);\n if (employeeEntity is null)\n throw new EmployeeNotFoundException(companyId);\n var employeeToPatch = _mapper.Map<EmployeeForUpdateDto>(employeeEntity);\n return (employeeToPatch, employeeEntity);\n}\npublic void SaveChangesForPatch(EmployeeForUpdateDto employeeToPatch, Employee employeeEntity)\n{\n _mapper.Map(employeeToPatch, employeeEntity);\n _repository.Save();\n}<\/code><\/pre>\nIn the first method, we are trying to fetch both the company and employee from the database and if we can\u2019t find either of them, we stop the execution flow and return the NotFound response to the client. Then, we map the employee entity to the EmployeeForUpdateDto type and return both objects (employeeToPatch and employeeEntity) inside the Tuple to the controller.
\n\u5728\u7b2c\u4e00\u79cd\u65b9\u6cd5\u4e2d\uff0c\u6211\u4eec\u5c1d\u8bd5\u4ece\u6570\u636e\u5e93\u4e2d\u83b7\u53d6\u516c\u53f8\u548c\u5458\u5de5\uff0c\u5982\u679c\u627e\u4e0d\u5230\u4ed6\u4eec\u4e2d\u7684\u4efb\u4f55\u4e00\u4e2a\uff0c\u6211\u4eec\u5c06\u505c\u6b62\u6267\u884c\u6d41\u5e76\u5c06 NotFound \u54cd\u5e94\u8fd4\u56de\u7ed9\u5ba2\u6237\u7aef\u3002\u7136\u540e\uff0c\u6211\u4eec\u5c06 employee \u5b9e\u4f53\u6620\u5c04\u5230 EmployeeForUpdateDto \u7c7b\u578b\uff0c\u5e76\u5c06 Tuple \u4e2d\u7684\u4e24\u4e2a\u5bf9\u8c61\uff08employeeToPatch \u548c employeeEntity\uff09\u8fd4\u56de\u7ed9\u63a7\u5236\u5668\u3002<\/p>\n
The second method just maps from emplyeeToPatch to employeeEntity and calls the repository's Save method.
\n\u7b2c\u4e8c\u4e2a\u65b9\u6cd5\u53ea\u662f\u4ece emplyeeToPatch \u6620\u5c04\u5230 employeeEntity\uff0c\u5e76\u8c03\u7528\u5b58\u50a8\u5e93\u7684 Save \u65b9\u6cd5\u3002<\/p>\n
Now, we can modify our controller:
\n\u73b0\u5728\uff0c\u6211\u4eec\u53ef\u4ee5\u4fee\u6539\u6211\u4eec\u7684\u63a7\u5236\u5668\uff1a<\/p>\n
[HttpPatch("{id:guid}")]\npublic IActionResult PartiallyUpdateEmployeeForCompany(Guid companyId, Guid id, [FromBody] JsonPatchDocument<EmployeeForUpdateDto> patchDoc)\n{\n if (patchDoc is null)\n return BadRequest("patchDoc object sent from client is null.");\n var result = _service.EmployeeService.GetEmployeeForPatch(companyId, id, compTrackChanges: false, empTrackChanges: true);\n patchDoc.ApplyTo(result.employeeToPatch);\n _service.EmployeeService.SaveChangesForPatch(result.employeeToPatch, result.employeeEntity);\n return NoContent();\n}<\/code><\/pre>\nYou can see that our action signature is different from the PUT actions. We are accepting the JsonPatchDocument from the request body. After that, we have a familiar code where we check the patchDoc for null value and if it is, we return a BadRequest. Then we call the service method where we map from the Employee type to the EmployeeForUpdateDto type; we need to do that because the patchDoc variable can apply only to the EmployeeForUpdateDto type. After apply is executed, we call another service method to map again to the Employee type (from employeeToPatch to employeeEntity) and save changes in the database. In the end, we return NoContent.
\n\u60a8\u53ef\u4ee5\u770b\u5230\u6211\u4eec\u7684\u4f5c\u7b7e\u540d\u4e0e PUT\u4f5c\u4e0d\u540c\u3002\u6211\u4eec\u6b63\u5728\u63a5\u53d7\u6765\u81ea\u8bf7\u6c42\u6b63\u6587\u7684 JsonPatchDocument\u3002\u4e4b\u540e\uff0c\u6211\u4eec\u6709\u4e00\u4e2a\u719f\u6089\u7684\u4ee3\u7801\uff0c\u6211\u4eec\u5728\u5176\u4e2d\u68c0\u67e5 patchDoc \u662f\u5426\u4e3a null \u503c\uff0c\u5982\u679c\u4e3a\u7a7a\uff0c\u5219\u8fd4\u56de\u4e00\u4e2a BadRequest\u3002\u7136\u540e\uff0c\u6211\u4eec\u8c03\u7528\u670d\u52a1\u65b9\u6cd5\uff0c\u4ece\u5176\u4e2d Employee \u7c7b\u578b\u6620\u5c04\u5230 EmployeeForUpdateDto \u7c7b\u578b;\u6211\u4eec\u9700\u8981\u8fd9\u6837\u505a\uff0c\u56e0\u4e3a patchDoc \u53d8\u91cf\u53ea\u80fd\u5e94\u7528\u4e8e EmployeeForUpdateDto \u7c7b\u578b\u3002\u6267\u884c apply \u540e\uff0c\u6211\u4eec\u8c03\u7528\u53e6\u4e00\u4e2a\u670d\u52a1\u65b9\u6cd5\u518d\u6b21\u6620\u5c04\u5230 Employee \u7c7b\u578b\uff08\u4ece employeeToPatch \u5230 employeeEntity\uff09\u5e76\u5c06\u66f4\u6539\u4fdd\u5b58\u5728\u6570\u636e\u5e93\u4e2d\u3002\u6700\u540e\uff0c\u6211\u4eec\u8fd4\u56de NoContent\u3002<\/p>\n
Don\u2019t forget to include an additional namespace:
\n\u4e0d\u8981\u5fd8\u8bb0\u5305\u542b\u989d\u5916\u7684\u547d\u540d\u7a7a\u95f4\uff1a<\/p>\n
using Microsoft.AspNetCore.JsonPatch;<\/code><\/pre>\nNow, we can send a couple of requests to test this code:
\n\u73b0\u5728\uff0c\u6211\u4eec\u53ef\u4ee5\u53d1\u9001\u51e0\u4e2a\u8bf7\u6c42\u6765\u6d4b\u8bd5\u6b64\u4ee3\u7801\uff1a<\/p>\n
Let\u2019s first send the replace operation:
\n\u8ba9\u6211\u4eec\u9996\u5148\u53d1\u9001 replace\u4f5c\uff1a<\/p>\n
https:\/\/localhost:5001\/api\/companies\/C9D4C053-49B6-410C-BC78-2D54A9991870\/employees\/80ABBCA8-664D-4B20-B5DE-024705497D4A<\/a><\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1201.jpg\")
<\/p>\n
It works; we get the 204 No Content message. Let\u2019s check the same employee:
\n\u5b83\u6709\u6548;\u6211\u4eec\u6536\u5230 204 No Content \u6d88\u606f\u3002\u8ba9\u6211\u4eec\u68c0\u67e5\u540c\u4e00\u540d\u5458\u5de5\uff1a<\/p>\n
https:\/\/localhost:5001\/api\/companies\/C9D4C053-49B6-410C-BC78-2D54A9991870\/employees\/80ABBCA8-664D-4B20-B5DE-024705497D4A<\/a><\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1202.jpg\")
<\/p>\n
And we see the Age property has been changed.
\n\u6211\u4eec\u770b\u5230 Age \u5c5e\u6027\u5df2\u66f4\u6539\u3002<\/p>\n
Let\u2019s send a remove operation in a request:
\n\u8ba9\u6211\u4eec\u5728\u8bf7\u6c42\u4e2d\u53d1\u9001\u4e00\u4e2a remove\u4f5c\uff1a<\/p>\n
![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1203.jpg\")
<\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1204.jpg\")
<\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1205.jpg\")
<\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1206.jpg\")
<\/p>\n