{{ message }}
Repository navigation
Renamed scalar still present in the schema if used as directive argument #2933
Description
Describe the bug
When custom scalar is used as a directive argument, old scalar name is still present in the schema after rename.
In the example below both Query.field return type and myDirective argument are updated to the Bar type but the schema contains entries for both original Foo and renamed Bar.
To Reproduce
Modify current scalar rename test to include directive (#2928)
scalar Foo
directive @myDirective(foo: Foo) on FIELD_DEFINITION
type Query {
field: Foo @myDirective
}See: dariuszkuc@6005e8e
It looks like the original Foo is only added if the directive is applied, i.e. if we update field: Foo @myDirective to field: Foo we won't have the old type in the schema. Might be an issue with applied directives.
Activity
Reproduction of #2933
bbakerman commentedon Aug 24, 2022
Thanks for reporting. I have created a reproduction test and can confirm it does not remove the old type if it used in applied schemas
Reproduction of #2933
bbakerman commentedon Aug 24, 2022
I can confirm that the old directive mechanism works (the type gets replaced) however the applied directive does not
Reproduction of #2933
Reproduction of #2933
Reproduction of #2933
andimarek commentedon Aug 24, 2022
We found the bug and fixed it ... see #2934
Reproduction of #2933