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

Disable generation of traits by default #11

Merged
merged 1 commit into from
Aug 15, 2017
Merged

Disable generation of traits by default #11

merged 1 commit into from
Aug 15, 2017

Conversation

jonas
Copy link
Contributor

@jonas jonas commented Aug 14, 2017

More work is needed to correctly generate traits for nested fragments.

@jonas
Copy link
Contributor Author

jonas commented Aug 14, 2017

Created #12 to reenable traits.

@@ -2,37 +2,28 @@ object HeroFragmentsApi {
case class HeroAppearancesAndInline(hero: HeroFragmentsApi.HeroAppearancesAndInline.Hero)
object HeroAppearancesAndInline {
case class HeroAppearancesAndInlineVariables()
case class Hero(name: Option[String], appearsIn: Option[List[Option[Episode]]], id: String) extends HeroFragmentsApi.Appearances
case class Hero(name: Option[String], appearsIn: Option[List[Option[Episode]]], id: String)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still seeing a lot of duplicate generated types, any way to reduce this?

More work is needed to correctly generate traits for nested fragments.
@jonas jonas merged commit c2f2891 into master Aug 15, 2017
@jonas jonas deleted the disable-trait-gen branch August 15, 2017 01:30
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

Successfully merging this pull request may close these issues.

None yet

2 participants