feat: optimize the UX of apisix-dashboard

[john1337]

Description

有没有考虑优化下apisix-dashboard的交互页面啊，对比了下higress的管理页面，apisix-dashboard的页面交互确实不太好用

[juzhiyuan]

@john1337 请问具体是什么？1、2、3、4、5？

[wklken]

@juzhiyuan

All the fields in the same form, even I only care about 30% of the fields.

• duplicated only one: URI and URIs, Host and Hosts, Remote Address and Remote Addresses; (only show one input field, and the user can add more, convert to URI or URIs by the count?)
• should hide the advanced parts, like Timeout, Keepalive Pool, Service Discovery, if the use want to use it, one more click to show the input fields
• don't show the form if the trigger is off, like TLS verify
• a or b， don't show both (node or service discovery)
• if type is roundrobin(default), the Hash on and Key should been hided

---

tldr:

• all fields, put a lot of pressure on me
• A bunch of nested grids， hard to figure out the nested relation.

---

[juzhiyuan]

duplicated only one: URI and URIs, Host and Hosts, Remote Address and Remote Addresses; (only show one input field, and the user can add more, convert to URI or URIs by the count?)

This will be considered in apache/apisix v4 (not determined yet)

should hide the advanced parts

No plans to allow sections to be shown or hidden by default. The current dashboard is mapped to the Admin API as much as possible.

if type is roundrobin(default), the Hash on and Key should been hided

This is indeed a good product improvement. So far, the Admin APIs have ensured that the input is valid.

[john1337]

我觉得可以参考下higress的管理页面，这两个入门门槛有些差距的

[SkyeYoung]

Hi, If you have ideas and time, feel free to submit proposals and PRs.

[SkyeYoung]

Also, PLEASE use English so that non-Chinese community members can read it.

[DSingh0304]

i will try to raise a PR in a few days after working on this...