Regular expressions examples in Intro

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

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
35/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
停滞
技术栈
markdown
领域
documentation

调研方向

Locate the Intro lesson lines 55–59 and compare the regular expression examples. Use “mark” consistently in the four examples, then check that each description still matches the pattern shown. The issue gives no filename or test to run; done means the examples use the same term and remain accurate.

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

描述

Use the same term for Lines 55-59

###I think using the same term "mark" is best for lines 56 to 59, easier to compare and allows instruction to ask for other terms using terms: word, comb, and respect.

- the regular expression `mark` will match not only `mark` but also find `marking`, `market`, `unremarkable`, and so on.
- the regular expression `\bmark` will match `mark`, `marking`, and `marketable`, but not 'remark' or 'demark'.
- the regular expression `mark\b` will match `mark` and `remark` but not `market`.
- the regular expression `\bmark\b` will match `mark` but not `marking' or `unremarkable`.

Thanks for contributing! If this contribution is for instructor training, please send an email to [email protected] with a link to this contribution so we can record your progress. You’ve completed your contribution step for instructor checkout just by submitting this contribution.

If this issue is about a specific episode within a lesson, please provide its link or filename.

Please keep in mind that lesson maintainers are volunteers and it may be some time before they can respond to your contribution. Although not all contributions can be incorporated into the lesson materials, we appreciate your time and effort to improve the curriculum. If you have any questions about the lesson maintenance process or would like to volunteer your time as a contribution reviewer, please contact The Carpentries Team at [email protected].


主要语言
没有语言数据
星标
36
派生
84
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

LibraryCarpentry/lc-data-intro 的其他 Issue

查看 LibraryCarpentry/lc-data-intro 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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