bug: Delete old generated code

[JavierSegoviaCordoba]

Expected behavior

When a type is removed from the GraphQL schema, generateJava task should delete the previous generated classes.

Actual behavior

The old classes are kept so it is necessary to delete them manually.

Steps to reproduce

• Create a type in the schema and run generateJava
• Remove that type from the schema, run generateJava and check how the old type is still there in the generated directory.

[berngp]

Did you tried calling 'clean' before 'generateJava'?

[JavierSegoviaCordoba]

That is not a recommended practice even if it works.

[srinivasankavitha]

We will look into a fix in the next week or two. In the meantime, if this is a more immediate problem for you, feel free to open a PR as we welcome contributions.

[JavierSegoviaCordoba]

I would have to check, but I think that deleting all files from the output directory before the codegen should be enough, as input are the same the task would still be cacheable and wouldn't run if they haven't changed 🤔

[JavierSegoviaCordoba]

Well, the approach I mentioned before is for the Gradle generateJavaTask. But probably it should be fixed in more places, not only there, if it has to be fixed only in Gradle, I can create a PR for it.