You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Making a complete GraphQL app across separate schema files and modules is now tricky. Each type that is used externally needs to be manually remapped, which is extremely tedious, produces tons of boilerplate and is fault-prone for large integrations.
Describe the solution you'd like
Allowing adding imports to codegen files via e.g. extending the already existing DataModelMapper.getImports() to not start with empty HashMap but to populate it from a config var would make this trivial. It could be named e.g. just imports or additionalImports,
Describe alternatives you've considered
Injecting that text via other setting, e.g. generatedAnnotation - impossible due to leading @ and extremely hackish anyway.
The text was updated successfully, but these errors were encountered:
FyiurAmron
changed the title
allow providing custom imports
allow providing additional custom imports
Nov 27, 2023
Is your feature request related to a problem? Please describe.
Making a complete GraphQL app across separate schema files and modules is now tricky. Each type that is used externally needs to be manually remapped, which is extremely tedious, produces tons of boilerplate and is fault-prone for large integrations.
Describe the solution you'd like
Allowing adding imports to codegen files via e.g. extending the already existing
DataModelMapper.getImports()
to not start with empty HashMap but to populate it from a config var would make this trivial. It could be named e.g. justimports
oradditionalImports
,Describe alternatives you've considered
Injecting that text via other setting, e.g.
generatedAnnotation
- impossible due to leading@
and extremely hackish anyway.The text was updated successfully, but these errors were encountered: