Skip to content

Commit bd960df

Browse files
committed
coding guidelines
1 parent 147fa6c commit bd960df

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

coding-guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ don't rely on anything impl specific.
101101
The default implementations for `Set` and `Map` should be the `LinkedHashSet` and `LinkedHashMap`
102102
because it offers stable iteration order.
103103

104-
### Stream API vs forEach, index loop etc
104+
### Stream API vs for, index loop etc
105105
Using the Stream API is ok in general, but it must kept simple. Stream maps inside
106106
maps should be avoided and the inner logic should be refactored into a method.
107107

@@ -174,7 +174,7 @@ method call should be on a new line:
174174
Every class/interface should have its one file in general.
175175
Inner classes are almost never ok (especially public ones). Every class should have its own file to make it easier to read and explore the code.
176176

177-
### User `graphql.Assert` instead of `Objects`
177+
### Use `graphql.Assert` instead of `Objects`
178178
We maintain our own small set of Assert util methods. Don't use `Objects.requireNonNull` and others in order
179179
to be consistent.
180180

0 commit comments

Comments
 (0)