Skip to content

【UI 页面功能请求】希望为配置列表、服务列表中的命名空间添加排序、检索功能 #12311

@WangJincheng4869

Description

@WangJincheng4869

Is your feature request related to a problem? Please describe.
当命名空间较多时,想要找到某个命名空间非常困难。

When there are many namespaces, it is very difficult to find a certain namespace.

Describe the solution you'd like

  1. 为配置列表、服务列表中的命名空间添加排序、检索功能。
  2. 配置列表、服务列表中命名空间和列表采用左右解构布局
  3. 可以为命名空间添加分组(仅为了方便管理),可以在配置列表、服务列表中使用 tree 结构显示。
  1. Add sorting and retrieval functions to the namespaces in the configuration list and service list.
  2. The namespaces and lists in the configuration list and service list adopt a left and right deconstruction layout
  3. Grouping can be added to namespaces (for ease of management only), and tree deconstruction can be used to display in configuration lists and service lists.

Describe alternatives you've considered
为配置列表、服务列表中的命名空间添加排序、检索功能。

Add sorting and retrieval functions to the namespaces in the configuration list and service list.

我的使用场景

其实 namespace 比较多我是在开发环境遇到的,线上环境如果项目不到一定的规模应该很难用到。

  1. 我们是统一安装了一个 nacos,每个开发人员会有自己的 namespace 作为自己的开发环境。
  2. 一个人可能开发多个项目,所有一个人就会有多个 namespace。
  3. UAT 环境也会用这个 nacos 环境,所以就会导致 namespace 特别的多。

问:为什么要都用一个 nacos 环境?
答:因为穷掉底了,电脑只装一个 IDEA 做开发都卡的一批,再装其他环境电脑干冒烟了也跑不动。

In fact, I encountered many namespaces in the development environment. If it is an online environment and the project is not of a certain scale, it should be difficult to use.

  1. We have installed a unified nacos, and each developer will have their own namespace as their own development environment.
  2. One person may develop multiple projects, so one person will have multiple namespaces.
  3. The UAT environment also uses this nacos environment, which leads to a particularly large number of namespaces.

Q: Why do we need to use the same nacos environment?
A: Because I am extremely poor, my computer only needs to install one batch of IDEA for development, and even if I install it in other environments, my computer won't be able to run even if it smokes.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions