\n\u6211\u4eec\u60f3\u8981\u5b9e\u73b0\u7684\u662f\u8fd9\u6837\u7684\uff1a
\nhttps:\/\/localhost:5001\/api\/companies\/companyId\/employees?searchTerm=MihaelFins<\/a><\/p>\n
This should return just one result: Mihael Fins. Of course, the search needs to work together with filtering and paging, so that\u2019s one of the things we\u2019ll need to keep in mind too.
\n\u8fd9\u5e94\u8be5\u53ea\u8fd4\u56de\u4e00\u4e2a\u7ed3\u679c\uff1aMihael Fins\u3002\u5f53\u7136\uff0c\u641c\u7d22\u9700\u8981\u4e0e\u8fc7\u6ee4\u548c\u5206\u9875\u4e00\u8d77\u5de5\u4f5c\uff0c\u6240\u4ee5\u8fd9\u4e5f\u662f\u6211\u4eec\u9700\u8981\u8bb0\u4f4f\u7684\u4e8b\u60c5\u4e4b\u4e00\u3002<\/p>\n
Like we did with filtering, we\u2019re going to extend our EmployeeParameters class first since we\u2019re going to send our search query as a query parameter:
\n\u5c31\u50cf\u6211\u4eec\u5bf9\u7b5b\u9009\u6240\u505a\u7684\u90a3\u6837\uff0c\u6211\u4eec\u5c06\u9996\u5148\u6269\u5c55\u6211\u4eec\u7684 EmployeeParameters \u7c7b\uff0c\u56e0\u4e3a\u6211\u4eec\u8981\u5c06\u641c\u7d22\u67e5\u8be2\u4f5c\u4e3a\u67e5\u8be2\u53c2\u6570\u53d1\u9001\uff1a<\/p>\n
namespace Shared.RequestFeatures;\n\npublic class EmployeeParameters : RequestParameters\n{\n public uint MinAge { get; set; }\n public uint MaxAge { get; set; } = int.MaxValue;\n public bool ValidAgeRange => MaxAge > MinAge;\n public string? SearchTerm { get; set; }\n}<\/code><\/pre>\nSimple as that.
\n\u5c31\u8fd9\u4e48\u7b80\u5355\u3002<\/p>\n
Now we can write queries with searchTerm=\u201dname\u201d in them.
\n\u73b0\u5728\u6211\u4eec\u53ef\u4ee5\u7f16\u5199\u5305\u542b searchTerm=\u201cname\u201d \u7684\u67e5\u8be2\u3002<\/p>\n
The next thing we need to do is actually implement the search functionality in our EmployeeRepository class:
\n\u63a5\u4e0b\u6765\u6211\u4eec\u9700\u8981\u505a\u7684\u662f\u5728\u6211\u4eec\u7684 EmployeeRepository \u7c7b\u4e2d\u5b9e\u9645\u5b9e\u73b0\u641c\u7d22\u529f\u80fd\uff1a<\/p>\n
public async Task<PagedList<Employee>> GetEmployeesAsync(Guid companyId,\n EmployeeParameters employeeParameters, bool trackChanges)\n{\n var employees = await FindByCondition(e => e.CompanyId.Equals(companyId), trackChanges)\n .FilterEmployees(employeeParameters.MinAge, employeeParameters.MaxAge)\n .Search(employeeParameters.SearchTerm)\n .OrderBy(e => e.Name)\n .ToListAsync();\n\n return PagedList<Employee>\n .ToPagedList(employees, employeeParameters.PageNumber, employeeParameters.PageSize);\n}<\/code><\/pre>\nWe have made two changes here. The first is modifying the filter logic and the second is adding the Search method for the searching functionality.
\n\u6211\u4eec\u5728\u6b64\u5904\u8fdb\u884c\u4e86\u4e24\u9879\u66f4\u6539\u3002\u7b2c\u4e00\u4e2a\u662f\u4fee\u6539\u7b5b\u9009\u903b\u8f91\uff0c\u7b2c\u4e8c\u4e2a\u662f\u6dfb\u52a0 Search \u641c\u7d22\u529f\u80fd\u7684\u65b9\u6cd5\u3002<\/p>\n
But these methods (FilterEmployees and Search) are not created yet, so let\u2019s create them.
\n\u4f46\u662f\u8fd9\u4e9b\u65b9\u6cd5\uff08FilterEmployees \u548c Search\uff09\u5c1a\u672a\u521b\u5efa\uff0c\u56e0\u6b64\u8ba9\u6211\u4eec\u521b\u5efa\u5b83\u4eec\u3002<\/p>\n
In the Repository project, we are going to create the new folder Extensions and inside of that folder the new class RepositoryEmployeeExtensions:
\n\u5728 Repository \u9879\u76ee\u4e2d\uff0c\u6211\u4eec\u5c06\u521b\u5efa\u65b0\u6587\u4ef6\u5939 Extensions\uff0c\u5e76\u5728\u8be5\u6587\u4ef6\u5939\u5185\u521b\u5efa\u65b0\u7c7b RepositoryEmployeeExtensions\uff1a<\/p>\n
using Entities.Models;\n\nnamespace Repository.Extensions;\n\npublic static class RepositoryEmployeeExtensions\n{\n public static IQueryable<Employee> FilterEmployees(this IQueryable<Employee> employees, uint minAge, uint maxAge) =>\n employees.Where(e => (e.Age >= minAge && e.Age <= maxAge));\n\n public static IQueryable<Employee> Search(this IQueryable<Employee> employees, string searchTerm)\n {\n if (string.IsNullOrWhiteSpace(searchTerm))\n return employees;\n\n var lowerCaseTerm = searchTerm.Trim().ToLower();\n\n return employees.Where(e => e.Name.ToLower().Contains(lowerCaseTerm));\n }\n}<\/code><\/pre>\nSo, we are just creating our extension methods to update our query until it is executed in the repository. Now, all we have to do is add a using directive to the EmployeeRepository class:
\n\u56e0\u6b64\uff0c\u6211\u4eec\u53ea\u662f\u5728\u521b\u5efa\u6269\u5c55\u65b9\u6cd5\u6765\u66f4\u65b0\u6211\u4eec\u7684\u67e5\u8be2\uff0c\u76f4\u5230\u5b83\u5728\u5b58\u50a8\u5e93\u4e2d\u6267\u884c\u3002\u73b0\u5728\uff0c\u6211\u4eec\u6240\u8981\u505a\u7684\u5c31\u662f\u5411 EmployeeRepository \u7c7b\u6dfb\u52a0\u4e00\u4e2a using \u6307\u4ee4\uff1a<\/p>\n
using Repository.Extensions;<\/code><\/pre>\nThat\u2019s it for our implementation. As you can see, it isn\u2019t that hard since it is the most basic search and we already had an infrastructure set.
\n\u8fd9\u5c31\u662f\u6211\u4eec\u7684\u5b9e\u65bd\u3002\u5982\u60a8\u6240\u89c1\uff0c\u8fd9\u5e76\u4e0d\u96be\uff0c\u56e0\u4e3a\u5b83\u662f\u6700\u57fa\u672c\u7684\u641c\u7d22\uff0c\u800c\u4e14\u6211\u4eec\u5df2\u7ecf\u8bbe\u7f6e\u4e86\u57fa\u7840\u8bbe\u65bd\u3002<\/p>\n
18.3 Testing Our Implementation<\/h2>\n
18.3 \u6d4b\u8bd5\u6211\u4eec\u7684\u5b9e\u73b0<\/p>\n
Let\u2019s send a first request with the value Mihael Fins for the search term:\u200c
\n\u8ba9\u6211\u4eec\u53d1\u9001\u7b2c\u4e00\u4e2a\u8bf7\u6c42\uff0c\u641c\u7d22\u8bcd\u7684\u503c\u4e3a Mihael Fins\uff1a<\/p>\n
https:\/\/localhost:5001\/api\/companies\/c9d4c053-49b6-410c-bc78-2d54a9991870\/employees?searchTerm=MihaelFins<\/a><\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1801.jpg\")
<\/p>\n
This is working great.
\n\u8fd9\u6548\u679c\u5f88\u597d\u3002<\/p>\n
Now, let\u2019s find all employees that contain the letters \u201cae\u201d:
\n\u73b0\u5728\uff0c\u8ba9\u6211\u4eec\u67e5\u627e\u5305\u542b\u5b57\u6bcd \u201cae\u201d \u7684\u6240\u6709\u5458\u5de5\uff1a<\/p>\n
![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1802.jpg\")
<\/p>\n![\"alt](\"\/images\/ultimateaspnetcorewebapi6\/1803.jpg\")
<\/p>\n