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

Allows modules to not provide any type definition if they provide at least one provider #2471

Open
darkbasic opened this issue Nov 4, 2023 · 0 comments

Comments

@darkbasic
Copy link
Contributor

In Accounts.js 1.0 certain modules like the mongo module are in charge to solely provide a DatabaseInterfaceUserToken or a DatabaseInterfaceSessionsToken: they basically implement a known interface which other modules can use to access either the database used to store user data or the one used to store sessions.
Unfortunately graphql-modules complains about missing typeDefs so I had to work it around by passing fake ones.
Another use case could be modules used solely to provide services consumed by REST-only users.
In either case we shouldn't be forced to provide typeDefs in each and every module if we want to allow the user to use modules to piece together their application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant