承接 andrey-helldar/api-response 相关项目开发

从需求分析到上线部署,全程专人跟进,保证项目质量与交付效率

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

andrey-helldar/api-response

最新稳定版本:v10.0.0

Composer 安装命令:

composer require andrey-helldar/api-response

包简介

Package for standardizing the responses from the API of your Symfony based applications.

README 文档

README

API Response

Stable Version Unstable Version Total Downloads License

Package for standardizing the responses from the API of your Symfony based applications.

Getting Started

Upgrade guides

[ to top ]

Installation

To get the latest version of API Response, simply require the project using Composer:

$ composer require dragon-code/api-response

This command will automatically install the latest version of the package for your environment.

Instead, you may of course manually update your require block and run composer update if you so choose:

{
    "require": {
        "dragon-code/api-response": "^9.1"
    }
}

Alright! Use api_response() helper.

Compatibility table

Package version PHP min version Symfony version Support Links
^9.0 7.2.5 ^4.0, ^5.0, ^6.0 Supported Upgrade guide
^8.0 7.2.5 ^4.0, ^5.0 Not Supported Upgrade guide
^7.0 7.2.5 ^4.0, ^5.0 Not Supported Upgrade guide
^6.0 7.3 ^4.0, ^5.0 Not Supported Upgrade guide
^5.0 7.1.3 ^4.0, ^5.0 Not Supported ---
^4.4.1 5.6.9 ^3.0, ^4.0, ^5.0 Not Supported ---
^4.0 5.6.9 ^3.0, ^4.0 Not Supported ---

[ to top ]

Using

Use with data key

as NULL with code:

// php 7.4 and below
return api_response(null, 304);

// php 8.0
return api_response( status_code: 304 );

return with code 304:

{
    "data": null
}

[ to top ]

as integer with default code:

return api_response(304);

return with code 200:

{
    "data": 304
}

[ to top ]

as string with default code:

return api_response('qwerty');

return with code 200:

{
    "data": "qwerty"
}

[ to top ]

as string with code:

return api_response('qwerty', 400);

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "qwerty"
    }
}

[ to top ]

as integer with code:

return api_response(304, 400);

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": 304
    }
}

[ to top ]

as array:

$data = [
    [
        'title' => 'Title #1',
        'description' => 'Description #1',
    ],
    [
        'title' => 'Title #2',
        'description' => 'Description #2',
    ],
];

[ to top ]

as error

return api_response($data, 400);

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": [
            {
                "title": "Title #1",
                "description": "Description #1"
            },
            {
                "title": "Title #2",
                "description": "Description #2"
            }
        ]
    }
}

[ to top ]

as success

return api_response($data);

return with code 200:

{
    "data": [
        {
            "title": "Title #1",
            "description": "Description #1"
        },
        {
            "title": "Title #2",
            "description": "Description #2"
        }
    ]
}

If the first parameter is a number, then the decryption of the error by code will be return. In other cases, the value of the passed variable will be return.

[ to top ]

with additional content

// php 7.4 and below
return api_response('title', 200, ['foo' => 'bar']);
// or
return api_response('title', null, ['foo' => 'bar']);

// php 8.0
return api_response('title', with: ['foo' => 'bar']);

return with code 200:

{
    "data": "title",
    "foo": "bar"
}

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "ok"
    },
    "foo": "bar"
}
return api_response(['data' => 'foo', 'bar' => 'baz']);

return with code 200:

{
    "data": "foo",
    "bar": "baz"
}

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "foo"
    },
    "bar": "baz"
}

[ to top ]

Use without data key

Since the goal of the package is to unify all the answers, we moved the variable definitions into a static function. So, for example, to enable or disable wrapping content in the data key, you need to call the wrapped or withoutWrap method:

use DragonCode\ApiResponse\Services\Response;

Response::withoutWrap();

as NULL with code and without data key:

// php 7.4 and below
return api_response(null, 304);

// php 8.0
return api_response( status_code: 304 );

return with code 304:

[]

[ to top ]

as integer with default code and without data key:

return api_response(304, 200);

return with code 200:

304

[ to top ]

as string with default code and without data key:

return api_response('qwerty', 200);

return with code 200:

"qwerty"

[ to top ]

as string with code and without data key:

return api_response('qwerty', 400);

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "qwerty"
    }
}

[ to top ]

as integer with code and without data key:

return api_response(304, 400);

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": 304
    }
}

[ to top ]

as array and without data key:

$data = [
    [
        'title' => 'Title #1',
        'description' => 'Description #1',
    ],
    [
        'title' => 'Title #2',
        'description' => 'Description #2',
    ],
];

as error and without data key

return api_response($data, 400);

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": [
            {
                "title": "Title #1",
                "description": "Description #1"
            },
            {
                "title": "Title #2",
                "description": "Description #2"
            }
        ]
    }
}

[ to top ]

as success and without data key

return api_response($data, 200);
// or
return api_response($data);

return with code 200:

[
    {
        "title": "Title #1",
        "description": "Description #1"
    },
    {
        "title": "Title #2",
        "description": "Description #2"
    }
]

If the first parameter is a number, then the decryption of the error by code will be return. In other cases, the value of the passed variable will be return.

[ to top ]

with additional content and without data key:

// php 7.4 and below
return api_response('title', 200, ['foo' => 'bar']);

// php 8.0
return api_response('title', with: ['foo' => 'bar']);

return with code 200:

{
    "data": "title",
    "foo": "bar"
}

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "ok"
    },
    "foo": "bar"
}
return api_response(['data' => 'foo', 'bar' => 'baz']);

return with code 200:

{
    "data": "foo",
    "bar": "baz"
}

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "foo"
    },
    "bar": "baz"
}

[ to top ]

No extra data

In some cases, when returning answers, you must also give additional data. Such as stack trace, for example.

To prevent this data from getting in response to production, you can globally set a label to show or hide this data:

use DragonCode\ApiResponse\Services\Response;

env('APP_DEBUG')
    ? Response::allowWith()
    : Response::withoutWith();

Now all responses will not contain the additional data being passed.

For example:

// php 7.4 and below
return api_response('title', 200, ['foo' => 'bar']);
// or
return api_response('title', null, ['foo' => 'bar']);

// php 8.0
return api_response('title', with: ['foo' => 'bar']);

return with code 200:

{
    "data": "title"
}

return with code 400:

{
    "error": {
        "type": "Exception",
        "data": "ok"
    }
}

Server Errors

Note: The $with parameter is also responsible for displaying server-side error messages.

In this case, Http errors will be displayed without masking.

For example:

use DragonCode\ApiResponse\Services\Response;

Response::allowWith();

$e = new Exception('Foo', 0);

return api_response($e);

return with code 500:

{
    "error": {
        "type": "Exception",
        "data": "Foo"
    }
}

and

use DragonCode\ApiResponse\Services\Response;

Response::withoutWith();

$e = new Exception('Foo', 0);

return api_response($e);

return with code 500:

{
    "error": {
        "type": "Exception",
        "data": "Whoops! Something went wrong."
    }
}

return with if code >=400 and < 500:

{
    "error": {
        "type": "Exception",
        "data": "Foo"
    }
}

[ to top ]

Returning exception instances

class FooException extends \Exception
{
    public function __construct()
    {
        parent::__construct('Foo', 405);
    }
}

class BarException extends \Exception
{
    public function __construct()
    {
        parent::__construct('Bar');
    }
}

$foo = new FooException();
$bar = new BarException();
return api_response($foo);

return with code 405:

{
    "error": {
        "type": "FooException",
        "data": "Foo"
    }
}
return api_response($foo, 408);

return with code 408:

{
    "error": {
        "type": "FooException",
        "data": "Foo"
    }
}
return api_response($bar);

return with code 400:

{
    "error": {
        "type": "BarException",
        "data": "Bar"
    }
}
return api_response($bar, 408);

return with code 408:

{
    "error": {
        "type": "BarException",
        "data": "Bar"
    }
}

You can also add additional data:

return api_response($foo, 405, ['foo' => 'Bar']);
// or
return api_response($foo, 0, ['foo' => 'Bar']);

return with code 405:

{
    "error": {
        "type": "FooException",
        "data": "Foo"
    },
    "foo": "Bar"
}

[ to top ]

Best practice use with the Laravel and Lumen Frameworks

If you use the Laravel or Lumen framework, you can update the extends in the app\Exceptions\Handler.php file depending on your application version and needs:

Version \ Type API + WEB Only API
9.x DragonCode\ApiResponse\Exceptions\Laravel\Nine\Handler as ExceptionHandler DragonCode\ApiResponse\Exceptions\Laravel\Nine\ApiHandler as ExceptionHandler
8.x DragonCode\ApiResponse\Exceptions\Laravel\Eight\Handler as ExceptionHandler DragonCode\ApiResponse\Exceptions\Laravel\Eight\ApiHandler as ExceptionHandler
7.x DragonCode\ApiResponse\Exceptions\Laravel\Seven\Handler as ExceptionHandler DragonCode\ApiResponse\Exceptions\Laravel\Seven\ApiHandler as ExceptionHandler

If you did not add anything to this file, then delete everything properties and methods.

For example, as a result, a clean file will look like this:

<?php

namespace App\Exceptions;

use DragonCode\ApiResponse\Exceptions\Laravel\Nine\Handler as ExceptionHandler;

class Handler extends ExceptionHandler
{
    //
}

More examples:

<?php

namespace App\Exceptions;

// use DragonCode\ApiResponse\Exceptions\Laravel\Nine\Handler as ExceptionHandler;
use DragonCode\ApiResponse\Exceptions\Laravel\Nine\ApiHandler as ExceptionHandler;

// use DragonCode\ApiResponse\Exceptions\Laravel\Eight\Handler as ExceptionHandler;
// use DragonCode\ApiResponse\Exceptions\Laravel\Eight\ApiHandler as ExceptionHandler;

// use DragonCode\ApiResponse\Exceptions\Laravel\Seven\Handler as ExceptionHandler;
// use DragonCode\ApiResponse\Exceptions\Laravel\Seven\ApiHandler as ExceptionHandler;

class Handler extends ExceptionHandler
{
    //
}

[ to top ]

Json Resources

Now, if you pass a resource object or validator object, it will also be rendered beautifully:

use Illuminate\Http\Resources\Json\JsonResource;

/** @mixin \Tests\Fixtures\Laravel\Model */
final class Resource extends JsonResource
{
    public function toArray($request)
    {
        return [
            'foo' => $this->foo,
            'bar' => $this->bar,
        ];
    }

    public function with($request)
    {
        return ['baz' => 'Baz'];
    }
}
$model = Model::first();
$resource = MyResource::make($model);

return api_response($resource);

return with code 200:

{
    "data": {
        "foo": "Foo",
        "bar": "Bar"
    },
    "baz": "Baz"
}

If Response::withoutWrap()

{
    "foo": "Foo",
    "bar": "Bar",
    "baz": "Baz"
}

If Response::withoutWith()

{
    "data": {
        "foo": "Foo",
        "bar": "Bar"
    }
}

If Response::withoutWith() and Response::withoutWrap()

{
    "foo": "Foo",
    "bar": "Bar"
}

[ to top ]

Validation

$data = [
    'foo' => 'Foo',
    'bar' => 123,
    'baz' => 'https://foo.example'
];

$rules = [
    'foo' => ['required'],
    'bar' => ['integer'],
    'baz' => ['sometimes', 'url'],
];
$validator = Validator::make($data, $rules);

return $validator->fails()
    ? new ValidationException($validator)
    : $validator->validated();

If success:

{
    "data": {
        "foo": "Foo",
        "bar": 123,
        "baz": "https://foo.example"
    }
}

If failed:

{
    "error": {
        "type": "ValidationException",
        "data": {
            "foo": ["The foo field is required."],
            "bar": ["The bar must be an integer."],
            "baz": ["The baz format is invalid."]
        }
    }
}

[ to top ]

License

This package is licensed under the MIT License.

[ to top ]

andrey-helldar/api-response 适用场景与选型建议

andrey-helldar/api-response 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 8.49k 次下载、GitHub Stars 达 38, 最近一次更新时间为 2017 年 02 月 20 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「symfony」 「api」 「response」 「laravel」 「api response」 「lumen」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

我们在过去多个企业项目中使用过 andrey-helldar/api-response 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 andrey-helldar/api-response 我们能提供哪些服务?
定制开发 / 二次开发

基于 andrey-helldar/api-response 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 8.49k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 38
  • 点击次数: 24
  • 依赖项目数: 1
  • 推荐数: 0

GitHub 信息

  • Stars: 38
  • Watchers: 1
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2017-02-20