[Proposal] Adding Support for Custom GraphQL Types and Resolvers in Firebase Data Connect #7894
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for custom scalar types and resolvers in Firebase Data Connect. The implementation includes:
customTypes
andresolvers
fields toSchemaYaml
interfaceCurrently, there's an issue with the emulator binary where it returns an error when using custom scalar types:
This is a limitation in the current emulator binary and will require updates to the emulator itself to fully support custom types.
Example Configuration:
GraphQL Schema Usage:
Scenarios Tested
Note: The current PR only includes tests in validate.spec.ts. Additional testing, particularly for emulator integration, is recommended.
Sample Commands