Add an option to provide module for the custom scalar definitions #354
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
Currently, the definitions for the custom scalars have to specified in the parent (
super
) module.For example if you have a custom
DateTime
scalar it generates for youtype DateTime = super::DateTime;
This PR adds the option
custom_scalars_module
which can be used to specify the path to the module that contains the definitions for the custom scalars that are necessary for the generated query.For the above example, setting this option to
crate::custom_scalars
the generated code for theDateTime
scalar will betype DateTime = crate::custom_scalars::DateTime;
How it can be used
graphql-client generate query.graphql --schema-path schema.graphql --custom-scalars-module='crate::custom_scalars'
Closes #245