Enatega SingleVendor Admin Allowing Gap in Rider Username and Accepting Negative Values in Phone Number Field
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- typescript
- 领域
- frontend
调研方向
从 Enatega SingleVendor Admin 系统的骑手管理部分开始，并在 Chrome 中复现报告的两个输入：包含空格的 username 和负数电话号码。跟踪这些字段的验证，并确认两个无效值都会被拒绝；payload 未指定要运行的文件或测试。
由索引模型根据 Issue 内容生成。
描述
Describe the bug
I have identified two critical issues in the Enatega SingleVendor Admin system within the rider section. Firstly, the system currently allows users to create rider usernames with gaps, potentially leading to confusion and errors. Secondly, the system accepts negative values in the phone number field, which can impact the ability to contact and manage riders effectively.
To Reproduce
Steps to reproduce the behavior:
Issue 1 (Gap in Rider Username):
Log in to the Enatega SingleVendor Admin system.
Navigate to the rider management section.
Create or edit a rider profile.
Attempt to set a username with a gap (e.g., "john doe" instead of "johndoe").
Issue 2 (Negative Value in Phone Number Field):
Log in to the Enatega SingleVendor Admin system.
Navigate to the rider management section.
Create or edit a rider profile.
Attempt to input a negative value in the phone number field.
Expected behavior
Expected Behavior - Issue 1:
The system should validate and restrict users from creating usernames with gaps, ensuring consistency and preventing potential issues with user identification.
Expected Behavior - Issue 1:
The system should validate and restrict users from creating usernames with gaps, ensuring consistency and preventing potential issues with user identification.
Screenshots
image
Desktop:
Browser : chrome
Additional context
Please investigate and address these issues promptly to enhance the reliability and functionality of the Enatega SingleVendor Admin system.
Thank you for your attention to these matters.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
gray-mueller/full-stack-document-solution 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 67/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 68/100
查看 gray-mueller/full-stack-document-solution 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
getsentry/sentry-conventions#732 · 1 条评论 ·
维护者通常 1 天内回复
-
status:in-linear status:team-assigned team:nodes
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
motiondivision/motion#3955 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
equinor/prisma-decision-web#919 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 83/100