docs: clarify default parameter behavior in section Quickening it Up and fix Portuguese translation typo
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 40/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- ruby
调研方向
Open the "Quickening it Up" section of the tutorial and its Portuguese counterpart, and locate the paragraph describing the initialize default argument (content="" / conteudo=""). Compare the two texts: the English one needs the wording softened to say the default only applies when the argument is omitted, and the Portuguese one additionally carries a stray __. Make the prose match across translations with consistent inline code around parameter names, then view the rendered pages to confirm. Note an open pull request (#266) already targets this, so check it before starting to avoid duplicate work.
由索引模型根据 Issue 内容生成。
描述
Section: Quickening it Up
Description
The Ruby tutorial's explanation of the initialize method contains two issues:
1. Misleading explanation (identified in both English and Portuguese)
Both versions suggest that the default argument (content="" / conteudo="") guarantees the parameter is a string.
However, the default value only applies when the argument is omitted. Passing nil or another incompatible value explicitly can still cause an error.
Suggested wording (English):
"The default value content="" ensures that content is an empty string when no argument is provided."
Suggested wording (Portuguese):
"O valor padrão conteudo="" garante que conteudo seja uma string vazia quando nenhum argumento for informado."
2. Formatting typo (Portuguese only)
The Portuguese translation contains an unexpected __ in the paragraph explaining the default parameter. This does not appear in others version.
Expected behavior
- Both translations accurately describe Ruby's default argument behavior.
- The Portuguese version no longer contains the unintended
__. - Parameter names and values use consistent inline code formatting.
- 主要语言
- Ruby
- 星标
- 258
- 派生
- 113
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ruby/TryRuby 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 64/100
-
难度 4/5 3-5 天 新手友好度 25/100
-
难度 2/5 1-3 小时 新手友好度 48/100
-
难度 4/5 3-5 天 新手友好度 48/100
-
难度 4/5 3-5 天 新手友好度 25/100
相似的 Issue
-
🐛 bug 👩💻 équipe CE 🧑🏭 entreprises
难度 2/5 1-3 小时 新手友好度 76/100
betagouv/conseillers-entreprises#4808 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
yosiat/panko_serializer#250 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
cline/mcp-marketplace#3886 ·
-
难度 2/5 1-3 小时 新手友好度 78/100