Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Magmar & Pichu have Follow Me in their Move Data by Machine (TM's) while the move follow me has never been a TM

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

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
领域
api, data

调研方向

从 commit a57ebeff66bae380fb0f4c4eb4790bc85c1256b2 开始,并比较 Pichu 和 Magmar API 端点返回的招式条目。检查所引用的 Moves/54 和 Moves/67 条目,然后确认 Follow Me 不再被列为 Fire Red / Leaf Green 或 Colosseum 的 Machine move。

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

描述

When asking the API for the data for a few Pokémon I came across an issue where TM data for a move which never has been a TM was provided for 2 Pokémon. These Pokémon being Pichu and Magmar. After searching a bit, I came across commit: a57ebeff66bae380fb0f4c4eb4790bc85c1256b2

This commit has added the move to 3 Pokémon. But on 2 of these (Magmar, Pichu) it was added under move-learn-method : 4 which is "Machine"

Steps to Reproduce: (Pichu)

  1. Go to https://pokeapi.co/api/v2/pokemon/pichu
  2. Go to Moves/54
  3. This is where the Move "Follow me" is defined as TM for Fire Red / Leaf Green

Steps to Reproduce: (Magmar)

  1. Go to https://pokeapi.co/api/v2/pokemon/magmar
  2. Go to Moves/67
  3. This is where the Move "Follow me" is defined as TM for Colosseum

Expected Behavior:
When asking the API for the TM/HM data for Magmar and Pichu, it shouldn't include Follow Me

主要语言
Python
星标
5.4k
派生
1.2k
平均合并
2 天 12 小时
30 天内合并 PR
18

贡献指南

打开贡献指南

从这里开始

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

PokeAPI/pokeapi 的其他 Issue

查看 PokeAPI/pokeapi 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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