There are patterns within your style you can use to simplify the way you’re interacting with . Or any other Version Control System for that matter… code GIT To give you a rough idea of what you should be looking for, think of when need to list a whole bunch of arguments for a function. TLDR: This does not give the full picture, so I suggest you keep on reading… Here why: 1. Keeping arguments in one line will make the change less visible: 2. Putting every argument in a new line will result in simpler GIT diffs: (more on the last argument in the next point) Adding a trailing comma & moving the closing brackets to a new line, will result in simpler git diffs when reordering. 3. This is language-specific. Not all programming languages allow trailing commas. Unfortunately none of the languages I’m using on a daily basis (Java & Kotlin) allow them. Let’s look at Python: (if you didn’t know what I was talking about) Unfortunately for languages without trailing commas this has no positive effect, but you can still use this pattern as a way of learning good habits. After all, . Kotlin might get this feature in the future

BUNCH

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Git-aware code styling

Too Long; Didn't Read

Company Mentioned

Bartek Lipinski

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Git-aware code styling

Too Long; Didn't Read

Company Mentioned

Bartek Lipinski

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES