Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: Global Type Resolver #1985

Open
esfomeado opened this issue Aug 13, 2024 · 2 comments
Open

feature: Global Type Resolver #1985

esfomeado opened this issue Aug 13, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request investigate

Comments

@esfomeado
Copy link
Contributor

esfomeado commented Aug 13, 2024

Please read our contributor guide before
creating an issue. Also consider discussing your idea on
the discussion forum first.

Describe the Feature Request

As of now we have to add a @DGSTypeResolver for each type that we want to resolve.

If we have many types and they all behave the same way it becomes cumbersome to add a new one everytime we add a new interface/union.

Describe Preferred Solution

Allow somehow to costumize the default type resolver that uses the class name or provide one that is used as fallback.

Describe Alternatives

@esfomeado esfomeado added the enhancement New feature or request label Aug 13, 2024
@paulbakker paulbakker self-assigned this Sep 12, 2024
@mrvaruntandon
Copy link
Contributor

@esfomeado could you please share example code block that would explain the use of @DGSTypeResolver becoming cumbersome?

@esfomeado
Copy link
Contributor Author

@mrvaruntandon Creating a single @DGSTypeResolver is not cumbersome.

The issue is that you have to create one per interface that you have. So if you have thousands of interfaces you have to create thousands of type resolvers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request investigate
Projects
None yet
Development

No branches or pull requests

3 participants