Castform form/variety mixup

まず ID 351 の Pokémon エンドポイントと ID 351 の species エンドポイントを確認し、その後 issue #401 のフォームとバリエーションに関する説明を確認してください。Castform に記載されているフォーム、バリエーション、および form_description をプロジェクトが意図するモデルと比較します。完了条件は、このデータをどのように表現すべきかについて maintainer が確認した解決に到達することです。

Hello PokéAPI team :)

I'm currently playing around with the API and looking at the underlying data with interest. I note already that there is a lot of discussion around forms and varieties (am working based on the explanation: https://github.com/PokeAPI/pokeapi/issues/401.

Castform (id 351) has 1 form on its Pokémon object, and on the species object (id 351) , there are four variations listed with Pokémon IDs: 351, 10013 (Sunny), 10014 (Rainy), 10015 (Snowy).

Then these Pokémon IDs have their own equivalent form (form IDs 10028 (Sunny), 10029 (Rainy), 10030 (Snowy).

However, on the species object, there is a form description:

'Form changes along with type to match the weather in battle, due to forecast. Castform is always in its normal form outside of battle, regardless of weather'

But considering that the field is called form_description, this would not be correct, since its changing to a different variation. (The actual language itself within the field form_description is using form colloquially, I guess?)

So is Castform meant to have forms (similar to Arceus), which seems to contradict the description given of what Pokémon forms are, is the field form_description incorrectly populated for this instance, or should there be a variety_description field instead/as well, or have I completely misunderstood.

Steps to Reproduce:

1. Navigate to Pokémon endpoint with id 351 - only 1 form for Pokémon
2. Navigate to species endpoint with id 351 - Form description field is actually describing the variety differences.