Skip to content

Fix type resolvers for renamed polymorphic types and fix hooks signature #282

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

Merged
merged 1 commit into from
Jul 26, 2019

Conversation

dariuszkuc
Copy link
Collaborator

  • devs can use @GraphQLName annotation to rename the underlying types - this change updates interface and union type resolvers to retrieve correct name when resolving the types
  • update SchemaGeneratorHooks.didGenerateGraphQLType method to return the generated type instead of returning Unit, this makes it consistent with return type of other hook methods

* devs can use @GraphQLName annotation to rename the underlying types - this change updates interface and union type resolvers to retrieve correct name when resolving the types
* update SchemaGeneratorHooks.didGenerateGraphQLType method to return the generated type instead of returning Unit, this makes it consistent with return type of other hook methods
@codecov
Copy link

codecov bot commented Jul 26, 2019

Codecov Report

Merging #282 into master will decrease coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master     #282      +/-   ##
============================================
- Coverage     96.82%   96.82%   -0.01%     
  Complexity      196      196              
============================================
  Files            61       61              
  Lines           694      693       -1     
  Branches        124      124              
============================================
- Hits            672      671       -1     
  Misses            9        9              
  Partials         13       13
Impacted Files Coverage Δ Complexity Δ
...xpedia/graphql/generator/types/InterfaceBuilder.kt 100% <100%> (ø) 2 <0> (ø) ⬇️
...om/expedia/graphql/generator/types/UnionBuilder.kt 90% <100%> (ø) 2 <0> (ø) ⬇️
...otlin/com/expedia/graphql/generator/TypeBuilder.kt 100% <100%> (ø) 20 <4> (ø) ⬇️
.../com/expedia/graphql/hooks/SchemaGeneratorHooks.kt 93.33% <100%> (ø) 0 <0> (ø) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 44c643a...6bebe61. Read the comment docs.

@smyrick smyrick added changes: major Changes require a major version type: enhancement New feature or request labels Jul 26, 2019
@smyrick smyrick merged commit 1779807 into ExpediaGroup:master Jul 26, 2019
@dariuszkuc dariuszkuc deleted the fix_type_resolvers branch July 26, 2019 20:28
smyrick pushed a commit to smyrick/graphql-kotlin that referenced this pull request Sep 11, 2019
…ure (ExpediaGroup#282)

* devs can use @GraphQLName annotation to rename the underlying types - this change updates interface and union type resolvers to retrieve correct name when resolving the types
* update SchemaGeneratorHooks.didGenerateGraphQLType method to return the generated type instead of returning Unit, this makes it consistent with return type of other hook methods
dariuszkuc added a commit to dariuszkuc/graphql-kotlin that referenced this pull request Aug 5, 2022
…ure (ExpediaGroup#282)

* devs can use @GraphQLName annotation to rename the underlying types - this change updates interface and union type resolvers to retrieve correct name when resolving the types
* update SchemaGeneratorHooks.didGenerateGraphQLType method to return the generated type instead of returning Unit, this makes it consistent with return type of other hook methods
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes: major Changes require a major version type: enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

2 participants