在验证微信服务器的时候，提示： ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Call to undefined method Symfony\Component\HttpFoundation\Response::header() 我知道可能是dingo response的问题，我想自定义一个controller不使用dingo的response或者是不使用dingo的middleware，但是我是菜鸟，花了很长时间还是没有弄好， 请您看下是怎么回事

meta中的links格式问题，如果links为空，返回一个空数组，反之返回一个对象，这种数据不一致的情况算bug吗？具体源码出在这里\vendor\league\fractal\src\Serializer\ArraySerializer.php， $pagination['links'] = [];

    if ($currentPage > 1) {
        $pagination['links']['previous'] = $paginator->getUrl($currentPage - 1);
    }

    if ($currentPage < $lastPage) {
        $pagination['links']['next'] = $paginator->getUrl($currentPage + 1);
    }

这里如果 $pagination['links'] 没有值的情况下，直接就输入出了初始化的这个[]

http://lumen.jmqu.cn/auth/register post email:[email protected] password:xxxx { "message": "Declaration of ApiDemo\Repositories\Eloquent\BaseRepository::update() must be compatible with ApiDemo\Repositories\Contracts\RepositoryInterface::update(ApiDemo\Repositories\Contracts\int $id, array $attributes)", "code": 64, "status_code": 500 } 报这个错是什么原因？

您好，请问如何能统一dingo api返回的异常处理结构，现在一旦报异常，就只有messaage和status_code2个字段；比如我用laravel5.4的用户授权中，采用Policy方式，在路由中加can:update,**，来验证授权，一旦授权不允许，会返回 { "message": "This action is unauthorized.", "status_code": 500 }

我想自定义这个结构。

在本地调试的，不知道怎么回事，重新下载最新版，全新安装的也是这种情况 php version 5.6.27 + apache 我测试了https://lumen.lyyw.info/api/user 没有返回这个错误，请帮助看下，多谢 流程： 1.通过https://lumen.lyyw.info/api/users，post用户，得到token 2.通过https://lumen.lyyw.info/api/user header里面Authorization为：Bearer {token} 流程应该是没有问题的，用的postman调试的

我现在是这样子手动加载使用。我看见你的demo里面没有其他关于includeUser调用的代码。自己尝试了很久也没发现可以自动加载的。

return $this->response()
            ->paginator($articles, (new ArticleTransformer)->setDefaultIncludes(['user']));

//policy中修改资源的权限 UserOriResPolicy public function update(User $user,UserOriFiles $userOriFiles){ return $user->uid === $userOriFiles->author_id; }

// controller中的方法 public function update($id){ //侧路模式的权限判断

	$userOriFile = UserOriFiles::find($id);
	$isok = $this->authorize('update',$userOriFile);

最后接口一直报错 “This action is unauthorized”， google 上有这个问题，但没有回答，你有在项目中用到Policy 吗？

https://www.laracasts.com/discuss/channels/laravel/laravel-54-policies-not-working-with-jwt

file: app/Repositories/Eloquent/BaseRepository.php

public function where(array $data)
{
    $this->model = $this->model->where($data);
    return $this;
}

$model->where() will call the magic method __call, and get the new instance of '\Illuminate\Database\Eloquent\Builder' rather than the '\Illuminate\Database\Eloquent\Model'

First thing, thank you to create this very useful demo API in Lumen.

I have a question related to work around using PHP session in Lumen 5.2 and 5.3. I know it's removed in these version. Just wonder if you have any advice if I want to use Session.

Again thank you very much

Hi Yu Li, I don't know the best way to contact you. Do you consider writing this in English? Also do you have an English version of this -> http://oomusou.io/laravel/laravel-architecture/

➜ ~ homestead edit - map: h.lumen-api-demo to: /home/vagrant/Code/lumen-api-demo/public

/etc/hosts:

  127.0.0.1 h.luemn-api-demo

vagrant halt vagrant up -provision

➜ ~ curl http://h.lumen-api-demo:8000/api/auth/signin curl: (6) Could not resolve host: h.lumen-api-demo

app.php中把这个注释打开后报错，不太清楚这个逻辑，请问能讲下吗。 app('Dingo\Api\Auth\Auth')->extend('jwt', function ($app) { return new Dingo\Api\Auth\Provider\JWT($app['Tymon\JWTAuth\JWTAuth']); });

In Connection.php line 664:

could not find driver (SQL: select * from information_schema.tables where table_schema = chat and table _name = migrations)

In Connector.php line 67:

could not find driver

0. clone当前节点上的代码，composer install（删除掉vendor先）
1. 跨域的时候cors不生效，但是放到$app->middleware后生效。

$app->middleware([
    // 根据 accept-language 设置语言
    'locale' => App\Http\Middleware\ChangeLocale::class,
    'cors' => palanik\lumen\Middleware\LumenCors::class,
]);

$app->routeMiddleware([
    //'cors' => palanik\lumen\Middleware\LumenCors::class,
    'auth' => App\Http\Middleware\Authenticate::class,
    'serializer' => \Liyu\Dingo\SerializerSwitch::class,
]);

2. 另外这个第三放组件不管啥options请求都劫持并返回肯定是不好的。

    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure  $next
     * @return mixed
     */
    public function handle($request, Closure $next) {

        if ($request->isMethod('OPTIONS')) {
            $response = new Response("", 200);
        }
        else {
            $response = $next($request);
        }