dotnet add package NetUtilityKit --version 1.0.1

It ensures that the controller is clean and legible.
It allows you to give a stronger and different response. Different Overloads are available.
There is no need to do if else in the controller. You can manage this situation from a different layer.
If you don't want to repeat yourself, you can manage the controller part with a base class.
A simple example is presented.

Converting the filtering expression you receive as a string by the client to the expression type.
In this way, you can quickly perform powerful filtering operations with a single method.
You may need to set limits on filters for security.

Example- Service
    public async Task<ResponseModel<bool>> CreateItemAsync(CreateItemDto createItemDto, CancellationToken cancellationToken)
    {
        try
        {
            await AddItemAsync(createItemDto, cancellationToken);

            return ResponseModel<bool>.SuccessResponse(true, 201);
        }
        catch (Exception ex)
        {
            _logger.LogError(ex.Message);

            return ResponseModel<bool>.ErrorResponse($"{ex.Message}", 500);
        }
    }

Example- Controller

  [HttpPost]
    public async Task<IActionResult> Create(CreateItemDto createItemDto, CancellationToken cancellationToken)
    {
        var response = await _itemService.CreateItemAsync(createItemDto, cancellationToken);

        return new ObjectResult(response)
        {
            StatusCode = response.StatusCode
        };
    }

Example - Request Query And Body

public sealed record GetAllFilterCustomerQuery(
  string Expression
);

Example- Service

  public async Task<List<Customer>> GetAllFilter(GetAllFilterCustomerQuery request)
  {
     
      var expression = ExpressionParser.ParseExpression<Customer>(request.Expression);

      var query = _queryRepository.GetAll().Where(expression).Include(p => p.CustomerType).ToListAsync();    

      return result;

  }

Example - Request
{
  "expression": "x=> x.IsActive == true"
}