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

Link up --physical and --special Z moves to complete their data

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
领域
api

调研方向

首先检查 move ID 622–657 的 API 数据,对比物理 Z Moves 和特殊 Z Moves 及其 flavour-text 条目。检查这些 moves 和 GMax moves 的 learned_by_pokemon 字段,然后确认所请求的链接和数据填充是否符合预期,再验证受影响的 API 响应。

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

描述

The moves between 622 and 657, Z Moves, are usually identical to one another.

For example 623 is effectively the same as 622, with the only real difference being that one is physical, the other specia. I've not played S/M which is where I think this comes from - but I can understand the rational here.

The problem is that for the moves in that range id + 1 has Dummy Data in all of its Flavour Text entries. Could these be combined for completeness?

I also wanted to ask about the learned_by_pokemon fields on those moves (GMax as well). Is that data that's simply not been populated yet because of the sheer volume, or is this by choice? If every Pokémon of a certain type can temporarily use those?

主要语言
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 摘要。