currency at the half cent
维护者通常 4 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the Currency() constructor and its cmp method, which the issue says should round the correct answer to two decimals when the context forbids more than two decimal places. Reproduce the half-cent case with Currency(12.345) under the default tolerance, using the contextCurrency.pl context. Done means $12.35 is accepted, but only after the maintainer agrees on the approach, which the thread has not yet settled.
由索引模型根据 Issue 内容生成。
描述
Sometimes when using contextCurrency.pl, there is algebra that leads to a perl decimal version of an answer, and then you pass that decimal to the Currency() constructor to create an answer where students must use a dollar sign.
Sometimes, you are creating an answer like this one: Currency(12.345). And sometimes (depending on what produced that decimal value and whatever machine rounding error may be in play) the correct answer displays as $12.35, but neither $12.35 nor $12.34 will be accepted as correct when a student enters them, using the default tolerance. They are just at the cusp of the decimal tolerance. Also a student may not enter something like $12.345 with the default flags.
Perhaps the problem author should be aware of all this and round their decimals before passing them to the Currency() constructor. But maybe not, since maybe the Currency() object is supposed to retain deeper decimal precision if it gets used in further calculations. So I'm wondering if we could address this by tweaking the cmp method for a Currency object. What I'm thinking is, if the context disallows entering more than two decimal places, the correct answer should be rounded to two decimal places before it is actually compared to the student answer. Would that idea raise any objections? Of course this is something where I'm interested to hear from @dpvc.
- 主要语言
- Perl
- 星标
- 48
- 派生
- 78
- 平均合并
- 5 天 13 小时
- 30 天内合并 PR
- 9
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
openwebwork/pg 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 48/100
openwebwork/pg#1566 · 5 条评论 ·
维护者通常 4 天内回复
-
难度 5/5 一周以上 新手友好度 38/100
openwebwork/pg#1563 · 8 条评论 ·
维护者通常 4 天内回复
-
难度 4/5 1-2 天 新手友好度 50/100
openwebwork/pg#1560 · 10 条评论 ·
维护者通常 4 天内回复
-
难度 5/5 一周以上 新手友好度 12/100
openwebwork/pg#1542 · 1 条评论 ·
维护者通常 4 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
openwebwork/pg#1530 · 3 条评论 ·
维护者通常 4 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
openwebwork/webwork2#3295 ·
维护者通常 4 天内回复
-
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 天内回复