Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

User list: icons for edit and remove, rights as one field in the account form, labels with a capital

未关闭
#658 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@guidol-ive 已经在做这个了。

开始于 2026年10月28日。

  • #659 来自 @guidol-ive —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript
领域
frontend

调研方向

The issue identifies the user list in privileged-user settings and the account form, and links the rights choices to issue #650. Start by reviewing pull request #659 and the implementation of those settings and form; the payload names no files or tests. Done means the list uses edit and remove icons with the stated last-privileged-user rule, rights are one field visible only to privileged users, and field labels start with capitals.

由索引模型根据 Issue 内容生成。

描述

Component: User interface Impact: Medium Level: Easy Type: Enhancement Value: Users

Problem

The user list in the settings of a privileged user is hard to use:

  • Each row has up to three large text buttons: bewerken, verwijderen, and admin or ontadmin. A user who is no user any more has a fourth, reincarnate, which is untranslated.
  • Admin, ontadmin and reincarnate are really one choice: the rights of the user (privileged user, standard user, no user). They are spread over separate buttons, and the account form has an extra "ontadmin" button at the top.
  • Field labels begin with a lower-case letter on most forms ("gebruikersnaam:", "volledige naam:", "e-mail:"), but with a capital on others.

Proposal

  • Per row a pencil (edit) and a bin (make no user), as icons with a tooltip. The last privileged user gets no bin.
  • The rights become one field Rechten (Rights) in the account form behind the pencil, with the choices Geprivilegieerde gebruiker, Standaardgebruiker and Geen gebruiker (#650). Only a privileged user sees it.
  • Field labels begin with a capital everywhere.
主要语言
JavaScript
星标
5
派生
9
平均合并
18 小时 7 分钟
30 天内合并 PR
11

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PlanBCode/hypha 的其他 Issue

查看 PlanBCode/hypha 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。