hyperf-plus / admin Goto Github PK

请问有文档吗？

https://github.com/lphkxd/hyperf-admin/blob/master/app/Service/UserService.php
setToken

            $jwtBuilder = new JwtBuilder();
            $jwtBuilder->setIssuer('api');
            $jwtBuilder->setAudience($id);
            //这里用简写，来减少加密后密文大小
            $jwtBuilder->setJwtData(['a' => $id, 't' => $type, 'g' => $group, 'u' => $username]);
            $tokenObj = $this->jwt->createToken($jwtBuilder);
            $refreshObj = $this->jwt->createToken($jwtBuilder, Jwt::SCOPE_REFRESH);

改成

            $jwtBuilder = new JwtBuilder();
            $jwtBuilder->setIssuer('api');
            $jwtBuilder->setAudience($id);
$jwtBuilder->setExpiration(time()+config("jwt.ttl"));
            //这里用简写，来减少加密后密文大小
            $jwtBuilder->setJwtData(['a' => $id, 't' => $type, 'g' => $group, 'u' => $username]);
            $tokenObj = $this->jwt->createToken($jwtBuilder);

$jwtBuilder2 = clone $jwtBuilder;
      $jwtBuilder2->setExpiration(time()+config("jwt.refresh_ttl"));
      $jwtBuilder2->setScope("");
            $refreshObj = $this->jwt->createToken($jwtBuilder2, Jwt::SCOPE_REFRESH);

下面的refreshUser改法一样．
用这个程序学hyperf很爽，加油～！

数据库数据非常少 < 100条. 我用hyperf原生写的接口大约10ms左右....担心后面数据多起来之后,效率会不会更低......

文档是用啥写的啊

可以实现多租户吗？

如题，现在导出很不方便 希望加一个条件导出

通用性高一点,不要用sql.
我要改一下前缀都麻烦得很.

我需要在自定义dialog中传入当前行的数据，比如id，提交表单时候把这个id和表单数据一起提交到指定actions。请问应当调用哪个接口呢？目前我是通过item来实现的。这样会把id显示出来，不是很好。

谢谢。

您好

我在本地部署了该项目，并不能按我想要的方式工作，readme文档中也没有明确的指示

希望得到您的回答

public 目录下只有打包后的文件。源文件没有了，无法二次开发啊

权限管理--添加--授权节点，如果前缀带有admin的话，类似于ANY::/admin/menu/*的路由会搜索不到

Problem 1
- hyperf-plus/admin[v2.0.1, ..., v2.0.3] require hyperf-plus/ui ^1.0.0 -> satisfiable by hyperf-plus/ui[v1.0.7, ..., v1.x-dev].
- hyperf-plus/admin[v2.0.4, ..., v2.1.3] require hyperf/model-cache ^2.0.0 -> satisfiable by hyperf/model-cache[v2.0.0, ..., 2.2.x-dev].
- hyperf-plus/admin dev-old requires hyperf/cache ~1.1.0 -> found hyperf/cache[v1.1.0, ..., 1.1.x-dev] but it conflicts with your root composer.json require (~3.1.0).
- hyperf-plus/admin dev-v3-develop requires hyperf-plus/ui ^3.1 -> found hyperf-plus/ui[dev-luoxin, dev-v3-develop, v1.0.7, ..., v1.x-dev] but it does not match the constraint.
- hyperf-plus/admin[v0.1.0, ..., v0.1.3] require hyperf/command ~2.0.0 -> found hyperf/command[v2.0.0, ..., 2.0.x-dev] but it conflicts with your root composer.json require (~3.1.0).
- hyperf-plus/admin[v2.2, ..., v2.x-dev] require hyperf/redis ^2.0.0 -> found hyperf/redis[v2.0.0, ..., 2.2.x-dev] but it conflicts with your root composer.json require (~3.1.0).
- hyperf-plus/ui[v1.0.7, ..., v1.0.31] require hyperf/http-message ~2.0.0 -> found hyperf/http-message[v2.0.0, ..., 2.0.x-dev] but these were not loaded, likely because it conflicts with another require.
- hyperf-plus/ui[v1.0.32, ..., v1.0.53] require hyperf/http-message ^2.0 -> found hyperf/http-message[v2.0.0, ..., 2.2.x-dev] but these were not loaded, likely because it conflicts with another require.
- hyperf/model-cache[v2.0.0, ..., 2.0.x-dev] require hyperf/contract ~2.0.0 -> found hyperf/contract[v2.0.0, ..., 2.0.x-dev] but these were not loaded, likely because it conflicts with another require.
- hyperf/model-cache[v2.1.0-beta1, ..., 2.1.x-dev] require hyperf/contract ~2.1.0 -> found hyperf/contract[v2.1.0-beta1, ..., 2.1.x-dev] but these were not loaded, likely because it conflicts with another require.
- hyperf/model-cache[v2.2.0-beta1, ..., 2.2.x-dev] require hyperf/contract ~2.2.0 -> found hyperf/contract[v2.2.0-beta1, ..., 2.2.x-dev] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires hyperf-plus/admin * -> satisfiable by hyperf-plus/admin[dev-old, dev-v3-develop, v0.1.0, v0.1.1, v0.1.2, v0.1.3, v2.0.1, ..., v2.x-dev].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require hyperf-plus/admin:*" to figure out if any version is installable, or "composer require hyperf-plus/admin:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

使用oss上传文件时，组件设置的path()参数不起作用

V2版本的在线文档不能访问了，麻烦上传到github上面来吧

这么优秀的项目，就这么停了可惜了

非常不错的开发体验，加油哥们