Please do not disallow the `+` character in user IDs
维护者通常 4 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- perl
调研方向
The payload names no files, so start by searching the repository for the user ID validation rule and the code that extracts a user ID from the Canvas email, and check where + is rejected. Confirm the restriction applies in both places. Done means a user ID containing + is accepted and works through the Canvas login path. Check that the design question about allowed characters has been settled before you change the rule.
由索引模型根据 Issue 内容生成。
描述
This is a feature request to allow the + character as part of user IDs.
Why? One of the biggest difficulties for our WeBWorK setup is that I can't properly test Canvas integration without having a real student account in Canvas. The student account I was able to get in the end is tied to a special email with a + character in it. Gmail, as well as some other systems, support using [email protected] and treat it as equivalent to [email protected]. This makes it possible to use different variations on the same email address, all pointing to the same inbox.
Since WeBWorK is set up to extract the user ID from the email that Canvas sends, I end up with a user ID that contains a + character. The actual user ID that Canvas uses also has a + character (it's the full email).
Generally, allowing the + character would make it much easier for me to debug issues in out environment.
- 主要语言
- Perl
- 星标
- 164
- 派生
- 167
- 平均合并
- 6 天 7 小时
- 30 天内合并 PR
- 27
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
openwebwork/webwork2 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
openwebwork/webwork2#3295 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
openwebwork/webwork2#3290 ·
维护者通常 4 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
openwebwork/webwork2#2997 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 56/100
openwebwork/webwork2#3276 ·
维护者通常 4 天内回复
-
难度 4/5 3-5 天 新手友好度 52/100
openwebwork/webwork2#3272 · 6 条评论 ·
维护者通常 4 天内回复
查看 openwebwork/webwork2 的全部 Issue
相似的 Issue
-
nftables: "Display comment in rules list?" option has no effect, comments not shown in rules list未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Type: Bug
难度 2/5 1-3 小时 新手友好度 76/100
inverse-inc/packetfence#9707 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
RotherOSS/otobo#6457 · 2 条评论 ·
维护者通常 1 天内回复
-
The reply-to for the pro user signup emails should be the email of the user instrad of the contact@ email可能已有人在做 @sisodiaumang 今天认领。 未关闭🏭 producer platform - spam
难度 2/5 1-3 小时 新手友好度 66/100
openfoodfacts/openfoodfacts-server#15447 ·
维护者通常 1 天内回复
-
Harden argument handling in deploy-contract.sh可能已有人在做 @Asta-wizard 于 1 天前认领。 未关闭Stellar Wave
难度 2/5 1-3 小时 新手友好度 78/100
Feyisara2108/stellargive#1377 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复