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

Do not store standard types statically but keep them on the Schema instead #1183

Closed
ruudk opened this issue Jun 21, 2022 · 2 comments
Closed

Comments

@ruudk
Copy link
Contributor

ruudk commented Jun 21, 2022

When working with 2 schemas that have different standard types this becomes problematic.

For example, I have a schema that uses a custom ID type, but the other wants to use the default.

I can imagine this is not easily possible currently because of the way types are resolvable without a Schema (#1149).

@spawnia spawnia added this to the 16.0.0 milestone Jun 22, 2022
@spawnia
Copy link
Collaborator

spawnia commented Jun 22, 2022

This is a large breaking change, so I will plan this for v16.

Until then keep in mind that while static, the standard types can be manipulated dynamically. Unless you need to serve both schemas in the same execution context, you can work around this issue.

@ruudk
Copy link
Contributor Author

ruudk commented Aug 12, 2023

See issue #1424 for a possible solution

@ruudk ruudk closed this as completed Aug 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants