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

Missing evolution details for Runerigus in Legends Z-A

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
data

调研方向

Start from the existing near_special_rock handling for Leafeon and Glaceon, then check the evolution-details data for the Yamask line at https://pokeapi.co/api/v2/evolution-chain/287/. Find where evolution-details fields are defined and populated, and decide how to represent the under-arch requirement. Done when Runerigus has a Legends: Z-A evolution-details entry with the Coulant Waterway location and the arch condition, and the endpoint shows it.

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

描述

Describe the Bug

The evolution chain for the Yamask line is missing an evolution-details entry for Runerigus in Legends: Z-A. It should have one because the required location is different from Sword/Shield (in Z-A, it must be evolved at Coulant Waterway).

The evolution details that do exist for it also don't account for the special requirement that Runerigus must be evolved while standing under an arch. I think this would be best implemented as an additional boolean, similar to near_special_rock for Leafeon/Glaceon (it could also be considered a different, unique trigger, but all the other requirements are already handled by existing fields).

Steps to Reproduce
Resolving the Bug

Anyone is open to making a PR for this issue.

主要语言
Python
星标
5.4k
派生
1.2k
平均合并
1 天 23 小时
30 天内合并 PR
13

环境准备

从这里开始

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

PokeAPI/pokeapi 的其他 Issue

查看 PokeAPI/pokeapi 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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