Proposing a PR to fix a few small typos

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

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
python

调研方向

先检查明确列出的文件:restkit Python 模块和两个文档文件。严格按照描述更正每处拼写,然后检查列出的位置是否包含预期的词语,并确认没有意外更改。修复分支已经准备好,因此在重复这项工作之前请先协调。

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

描述

Issue Type

[x] Bug (Typo)

Steps to Replicate and Expected Behaviour

  • Examine restkit/resource.py and observe parameterss, however expect to see parameters.
  • Examine restkit/resource.py and observe optionnal, however expect to see optional.
  • Examine restkit/resource.py and observe additionnal, however expect to see additional.
  • Examine restkit/filters.py and observe agains, however expect to see against.
  • Examine restkit/filters.py and observe wicth, however expect to see which.
  • Examine restkit/client.py and observe unkown, however expect to see unknown.
  • Examine restkit/init.py and observe tupple, however expect to see tuple.
  • Examine doc/sitemap_gen.py and observe suppressable, however expect to see suppressible.
  • Examine doc/pool.rst and observe sesssion, however expect to see session.
  • Examine restkit/client.py and observe immediatly, however expect to see immediately.
  • Examine restkit/errors.py and observe happend, however expect to see happened.
  • Examine restkit/wrappers.py and observe appplication, however expect to see application.

Notes

Semi-automated issue generated by
https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

To avoid wasting CI processing resources a branch with the fix has been
prepared but a pull request has not yet been created. A pull request fixing
the issue can be prepared from the link below, feel free to create it or
request @timgates42 create the PR. Alternatively if the fix is undesired please
close the issue with a small comment about the reasoning.

https://github.com/timgates42/restkit/pull/new/bugfix_typos

Thanks.

主要语言
Python
星标
402
派生
69
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

benoitc/restkit 的其他 Issue

查看 benoitc/restkit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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