From 5e3e1c39c927cfe92514ec4da0ea2f9caed80d60 Mon Sep 17 00:00:00 2001 From: Tatu Saloranta Date: Sun, 17 Dec 2023 18:45:55 -0800 Subject: [PATCH] Minor clarifications to coding style doc --- contribution/jackson-coding-style-guide.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/contribution/jackson-coding-style-guide.md b/contribution/jackson-coding-style-guide.md index 0f94ff13..049e9c34 100644 --- a/contribution/jackson-coding-style-guide.md +++ b/contribution/jackson-coding-style-guide.md @@ -44,6 +44,10 @@ Import statements should be grouped and ordered in the following manner: 3. **Jackson Core Types**: Next, import Jackson core types, in the order of annotations, core, and databind. 4. **Component-Specific Types**: For non-core Jackson components, import component-specific types last. +Static import statements should be grouped after non-static ones, using same ordering. + +So, for example we might have: + ```java import java.io.*; // JDK imports import java.util.*; @@ -66,6 +70,8 @@ import com.fasterxml.jackson.other.modules.*; // and some Component-specific imp ### Field Naming +Standard Java Language naming recommendation (camel-case) is followed with following modifications: + - **Non-Public Fields**: Prefix non-public member fields with an underscore (e.g., `_fieldName`). ### Method Naming