René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Renamed scalar still present in the schema if used as directive argument","articleBody":"**Describe the bug**\r\nWhen custom scalar is used as a directive argument, old scalar name is still present in the schema after rename.\r\n\r\nIn 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`.\r\n\r\n**To Reproduce**\r\nModify current scalar rename test to include directive (https://github.com/graphql-java/graphql-java/pull/2928)\r\n\r\n```graphql\r\nscalar Foo\r\ndirective @myDirective(foo: Foo) on FIELD_DEFINITION\r\ntype Query {\r\n  field: Foo @myDirective\r\n}\r\n```\r\n\r\nSee: https://github.com/dariuszkuc/graphql-java/commit/6005e8e632fcc5c032203fbb0a54d86e399d2fce\r\n\r\nIt 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.\r\n","author":{"url":"https://github.com/dariuszkuc","@type":"Person","name":"dariuszkuc"},"datePublished":"2022-08-23T14:56:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2933/graphql-java/issues/2933"}