You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @kobylynskyi ! Can I ask you a question here?
I have bunch of graphql schemas from DataHub on top of which I want to write my own custom queries as we run from a GraphQL end point. How can I use this plugin to generate code for custom queries.
For example I tried to add an additional graphql file in the schemas folder for the plugin but could not see any code generated for my custom query. Any leads?
hey @upendrao
few questions:
1 - There's one folder with all the schemas and you created another file with your own queries?
2 - Does your schema file have an extend keyword? If you have queries spread across multiple files you would want to have extend type Query { ... } in every file.
3 - If the answer to questions 1 and 2 is yes, but you still don't see a code generated for your custom schema, then try keeping only your schemas in the folder (deleting all other) and see if classes are generated. You can investigate from there.
Let me know how it goes.
Hi,
If I use 'extend type Query {' then I think I need to implement that query
on my own as it wont exist on GraphQL server.
For example I have a query as follows then I want to generate Java/Kotlin
code for that query so that I can easily deserialize the response into it.
query {
listDomains(
input: {}
) {
start
count
total
domains {
urn
properties {
name
}
}
}
}
The types defined in the base schema (ex: Domain here) have a mix of
nullable and non-nullable fields.
But in a query projection we (want to)list only a subset of the fields of a
specific type.
I am experiencing a challenge while deserializing such types when the
projection does not include a non-nullable field.
Is there any fix for this on the json codec?
Best Regards,
Upendra
On Fri, Mar 31, 2023 at 3:30 PM Bogdan Kobylynskyi ***@***.***> wrote:
hey @upendrao <https://github.com/upendrao>
few questions:
1 - There's one folder with all the schemas and you created another file
with your own queries?
2 - Does your schema file have an extend keyword? If you have queries
spread across multiple files you would want to have extend type Query {
... } in every file.
3 - If the answer to questions 1 and 2 is *yes*, but you still don't see
a code generated for your custom schema, then try keeping only your schemas
in the folder (deleting all other) and see if classes are generated. You
can investigate from there.
Let me know how it goes.
—
Reply to this email directly, view it on GitHub
<#1046 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7BMZXCURMXBVX7LNWOWIDW63L7FANCNFSM6AAAAAAV5CYIEQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Related to #1045
Updated following dependencies to resolve security vulnerabilities
com.graphql-java:graphql-javacom.fasterxml.jackson.core:jackson-databindUpdated unit tests to be able to parse test schemas with more tokens than the default size(15000)
Changes were made to: