Skip to content

Conversation

@guy120494
Copy link

Resolving #164

result
} else {
val wrapper = options
.genericWrappers
Copy link
Contributor

Choose a reason for hiding this comment

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

should cs fixes be included in feature pr?

Copy link
Author

Choose a reason for hiding this comment

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

Im using intellij and when I push it fixes lines automatically.
It's only cs fixes, so it doesn't matter

Copy link
Contributor

Choose a reason for hiding this comment

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

Well, that actually matters because

  • it makes PR more lines to read
  • the PR affects lines that have nothing to do with the feature, meaning it's more difficult to find why/when the initial fix was made

Just saying, no cs configuration is included in the project anyway.

Copy link
Author

Choose a reason for hiding this comment

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

Ok. so I won't do it next time

@oliemansm oliemansm merged commit b864c4b into graphql-java-kickstart:master Aug 25, 2018
@oliemansm oliemansm modified the milestone: 5.3.1 Sep 30, 2018
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.

4 participants