TypeResolver | 5 based resolver of Class names

As said in the comments, you should look in your Hangfire database for a serialized parameter featuring a ISet. It is the deserialization of this parameter which causes the issue, as indicated by :

You don't have the dependency for that type. Just add this to your gradle file

Turns out, Hangfire itself does not work great when multiple apps use the same sql schema. To solve this problem I used Hangfire.MAMQSqlExtension. It is a third-party extension but the repo says that it is officially recognized by Hangfire. If you are using the same schema for multiple apps, you have to use this extension in all your apps.

If your apps have different versions alive at the same time (e.g. production, test, development) this app itself does not fully work for failed jobs. If a job fails, regular Hangfire will not respect it's original queue, hence will move it to the default queue. Which will eventually create problems if you app only works with your app's queue or if the default queue is shared. To solve that issue, to force Hangfire to respect the original queue attribute, I used this solution. Which works great, and you get to name your app's queue depending on your web.config or appsettings.json.

My previous answer was deleted for some reason? This solves the problem and there's no other way. Do not delete the answer, for people who will experience this issue.

Found the solution:

Turns out, Hangfire itself does not work great when multiple apps use the same sql schema. To solve this problem I used Hangfire.MAMQSqlExtension. It is a third-party extension but the repo says that it is officially recognized by Hangfire. If you are using the same schema for multiple apps, you have to use this extension in all your apps.

If your apps have different versions alive at the same time (e.g. production, test, development) this app itself does not fully work for failed jobs. If a job fails, regular Hangfire will not respect it's original queue, hence will move it to the default queue. Which will eventually create problems if you app only works with your app's queue or if the default queue is shared. To solve that issue, to force Hangfire to respect the original queue attribute, I used this solution. Which works great, and you get to name your app's queue depending on your web.config or appsettings.json.

Here is an explanation on github

A module initializer is executed at, or sometime before, first access to any static field or first invocation of any method defined in the module.

I would suggest you to use an enum for this case:

After spending some time making changes, I finally got a working solution.

I had to make sure that typeDefs was an array of GraphQL Documents and not a type of [Function: types]. To do that, I removed unnecessary function syntax.

For example:

I replaced this export const types = () => [Book]; with this export const types = Book;

I replaced this types: () => [types, queryTypes, inputTypes, mutationTypes] with types: [types, queryTypes, inputTypes, mutationTypes]

... and pretty much every where I had () =>

Finally, before instantiating ApolloServer, instead of pushing tmp.types to the array of types, I used concat to use all defined graphql types in the I had defined the current file 'plus' the graphql types imported in every directory

typeDefs = typeDefs.concat(tmp.types);

The following is a rough (but correct) answer to my own question. Each of these statements takes a number of types (classes) and their methods and comfortably separates them based on criterion. Please note the generator will still generate (empty) classes regardless of them having any eligible members (methods) or not. This is why we are using a where clause in the parameter for types as well as using the WithMethods (with a parameter) in the second set of code.