Slash offers users an option to drop unused types and fields from a GraphQL perspective. So if the user had a type Temp with fields aaa and bbb in the initial schema and then removes it in the later versions, we need to list Temp as an unused type and Temp.aaa and Temp.bbb as unused fields so that the user can get rid unused data.
Dropping type Temp should ideally also remove Temp.aaa and Temp.bbb which is not happening right now. So even if the user deletes type Temp, we continue to show them Temp.aaa and Temp.bbb as unused fields. This is confusing and misleading. We can’t expect Slash users to understand DQL schema. So we can either make the behavior in sync or have GraphQL provide support for dropping unused types/fields. Either would work for us.
cc: @gja