http://apisix.iresty.com/apisix/dashboard/#/schema/routes/create

Now conditions and actions are mixed up, and users are not clear. It needs to be clearly separated into two different areas.

[root@localhost incubator-apisix-dashboard]# node -v
v10.16.3
[root@localhost incubator-apisix-dashboard]# yarn -v
1.19.2
[root@localhost incubator-apisix-dashboard]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
[root@localhost incubator-apisix-dashboard]#

ERROR Failed to compile with 2 errors 9:38:30 PM

error in /Data/apisix/incubator-apisix-dashboard/src/components/HeaderSearch/index.vue

ERROR in /Data/apisix/incubator-apisix-dashboard/src/components/HeaderSearch/index.vue
76:18 Generic type 'Fuse<T, O>' requires 2 type argument(s).
74 | private options: RouteConfig[] = []
75 | private searchPool: RouteConfig[] = []

76 | private fuse?: Fuse
| ^
77 |
78 | get routes() {
79 | return PermissionModule.routes

error in /Data/apisix/incubator-apisix-dashboard/src/views/login/index.vue

ERROR in /Data/apisix/incubator-apisix-dashboard/src/views/login/index.vue
105:10 Module '"../../../node_modules/vuex/types"' has no exported member 'Dictionary'.
103 | import { Component, Vue, Watch } from 'vue-property-decorator'
104 | import { Route } from 'vue-router'

105 | import { Dictionary } from 'vuex'
| ^
106 | import { Form as ElForm, Input } from 'element-ui'
107 | import { UserModule } from '@/store/modules/user'
108 | import { isValidUsername } from '@/utils/validate'

ERROR Build failed with errors.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

配置路由参数类型错误，urls、hosts选项不能录入
类型应该为input，select 的话需要有个可以配置选项的入口

http://apisix.iresty.com/apisix/dashboard/#/schema/routes/list

The page is too wide to see the right button. Instead, just keep the description, host, uri, plug-in information, and click "Edit" to display the other column points.

In addition, the "description" column is too wide and needs to be changed to automatically adjust the width according to the content.

dashboard 登录页面取消默认记住的账号密码，并提供修改账号密码的操作。

目前默认是记住的账号密码，且不清楚在哪里修改账号密码。

The dashboard login page cancels the default account password and provides the operation of modifying the account password.

At present, the default is to remember the account password, and it is not clear where to modify the account password.

这里如果没有select 只有 input的话 confirm一直是灰的无法点击

I think the same uri will hardly appear in different route.

Plugin serverless-pre-function function不可编辑

现在的做法是点击“添加插件”的按钮，弹出一个下拉列表来选择，这个方式交互比较复杂。
因为插件并不会很多，十来个，而且每个路由上同一个插件也只能绑定一个。
所以希望改为把所有插件都平铺开，排在前面的是用户已经选择的插件，并直接在插件名字下面显示插件的参数，点击可以进行修改。

Now the way is to click on the "Add Plug-in" button, pop up a drop-down list to select, this way of interaction is more complex.

Because there aren't many plug-ins, more than a dozen, and the same plug-in can only be bound to one plug-in per route.

So I hope to spread out all the plug-ins. The top one is the plug-ins that the user has chosen, and display the parameters of the plug-ins directly under the name of the plug-ins. Click to modify them.

https://github.com/nightwatchjs/nightwatch

• User Login
• Route (could waiting for #491)
• Route Group
• Upstream
• Plugins
• Consumer
• SSL

Reference

• https://pro.ant.design/docs/ui-test-cn
• Cypress

应答体：

{"node":{"nodes":[{"value":{"host":"host","plugins":{},"uri":"/hello","upstream_id":"2","service_id":"00000000000000041874","desc":"","remote_addr":"127.0.0.1"},"createdIndex":41875,"key":"/apisix/routes/00000000000000041875","modifiedIndex":41875},{"value":{"uri":"/{:.*}","upstream_id":2},"createdIndex":41838,"key":"/apisix/routes/2","modifiedIndex":41838}],"modifiedIndex":41837,"createdIndex":41837,"key":"/apisix/routes","dir":true},"action":"get"}

please fix other similar points.

route配置页面，编辑Service及Upstream 无法删除配置。

"请选择" -> "请输入后回车"

should be address

hi @lilien1010, I found one issue here, the user can select a null value option.

related PR #62

创建 route 的时候，因为缺少 service ，然后我去新建 service ，创建好后页面切回来发现之前创建 route 的页面内容全部没了。最好保留一下用户之前已经录入的信息。

when enter the router list ,the Action column out of views,we always need to scroll to the right, which is inconvenient

English version:

1. allow to select the filter
2. allow to delete existing conditions
3. the option host, remote address, and method, the user is allowed to enter multiple different values, use space as separator
4. necessary conditions: uri and service, others are optional

Chinese version:

1. 用户选择需要添加的过滤条件
2. 也可以对已有条件删除
3. 在 host、remote_addr 和 methods 选项中，均允许用户输入多个不同的值，空格分割
4. 必要条件：uri 和 服务，其他均为可选

Plugin

serverless-pre-function, serverless-post-function

Request

http://apisix.iresty.com/apisix/admin/schema/plugins/serverless-pre-function

Screenshot

Currently, some values are marks as any type, it's not good for further development.

The same as #19

If there are too many entries, it is not convenient to see and find, so can we add paging and corresponding fuzzy queries?

Issue description

Environment

• apisix version (cmd: apisix version): 0.9
• OS: alpine 3.7

Minimal test code / Steps to reproduce the issue

What's the actual result? (including assertion message & call stack if applicable)

What's the expected result?

proxy-rewrite headers 不可编辑

schema is here：https://github.com/iresty/apisix/blob/master/lua/apisix/schema_def.lua#L216

each time I input a new upstream or router, the list is always in different order,

which I think it will better to ordered by RouterId or Upstream ID

@moonming @membphis Do we need remove those unused dependencies? so that the Dashboard can be more slim but run faster.

https://github.com/apache/incubator-apisix-dashboard/blob/31cac84fc5f569f4c6b70e048c2bb6e9271bf3a2/NOTICE#L7

https://github.com/iresty/lua-resty-radixtree#new Add vars to the conditions for creating routing pages.

Specific examples in the https://github.com/iresty/lua-resty-radixtree/blob/master/t/vars.t test, search vars= { can be, need to support equal, greater, less than, not equal to these operators; vars has supported nginx built-in variables and args, these need to be prompted in the interface, if args necessity is the beginning of args_.

The certificate and private key's pem encoded data is about 64 bytes width, I think 80 bytes width may be good.