Standardize element ordering across header implementations #153
Description
Description
This issue tracks the need to standardize the ordering of elements (imports, methods, fields, etc.) across HTTP header implementations in the codebase.
Context
During the review of PR #146 (feat: Add operator== and hashCode on all header classes), various element ordering inconsistencies were identified that should be addressed in a separate PR to maintain focus on the core equality/hashCode implementation.
Areas of Concern
- Inconsistent import statement ordering
- Mixed ordering of class members (fields, constructors, methods)
- Inconsistent parameter ordering in method signatures
- Inconsistent ordering of equality/hashCode method placement
Related
- Original PR: feat: Add operator== and hashCode on all header classes #146
- User feedback: feat: Add operator== and hashCode on all header classes #146 (comment)
This issue should be addressed in a dedicated PR focused solely on element ordering standardization.