jinzhu/copier
Copier
Copier is a Go library that deep copies data between structs, maps, and slices using reflection-based field mapping and struct tag controls. At its core, it automatically transfers values by matching source and destination fields by name, type, and methods, creating fully independent copies of nested data structures to prevent shared references and unintended mutations.
The library distinguishes itself through tag-driven copy rules that give developers fine-grained control over the copying process. Struct tags can enforce mandatory field copying, exclude specific fields from transfer, or map fields with different names between source and destination types. It also supports automatic type coercion between compatible slice and map types, and can skip zero-value fields in the source to prevent overwriting existing destination data with empty values.
Beyond basic struct-to-struct copying, Copier handles copying between slices and maps with the same mapping rules, and can convert a single struct into a slice element. The library provides method-to-field resolution, allowing source methods to populate destination fields, and supports recursive deep copying of arbitrarily nested structures. Documentation and installation are available through the project's repository.
Features
- Struct-to-Struct Copiers - Copies values between structs by matching fields, methods, and tags for automatic data transfer.
- Deep Copying Libraries - Provides a deep copying library for creating independent duplicates of nested data structures.
- Go Struct Copiers - Deep copies values between Go structs, maps, and slices using field matching and struct tags.
- Reflection-Based Field Matchers - Matches struct fields by name, type, and tags using Go reflection for automatic value transfer.
- Method-to-Field Resolvers - Provides method-to-field resolution for populating destination fields from source method return values.
- Copy Rule Controllers - Controls copy behavior with struct tags to enforce, ignore, or rename fields during value transfer.
- Field Copy Exclusions - Provides struct tags to skip copying specific fields, preventing unwanted data transfer between structs.
- Copy Behavior Controllers - Uses struct tags to enforce, ignore, or rename fields during value transfer between types.
- Copy Control Tags - Uses struct tags to enforce, exclude, or rename fields during copy operations for fine-grained data transfer control.
- Struct-to-Struct Field Matchers - Implements reflection-based field matching between source and destination structs for automatic copying.
- Struct Tag Mapping Utilities - Controls copy behavior with struct tags to enforce, ignore, or rename fields during value transfer.
- Deep Copy Utilities - Creates fully independent copies of complex nested data structures to prevent shared references.
- Reflection-Based Data Mappers - Transfers data between Go types by matching fields, methods, and tags at runtime.
- Zero-Value Field Skipping - Skips zero-value source fields during copy to avoid overwriting existing destination data with empty values.
- Enforced Field Copiers - Enforces mandatory field copying with error or panic if the field is not populated.
- Map-to-Map Copiers - Copies key-value pairs between maps with automatic type conversion for compatible types.
- Slice-to-Slice Copiers - Copies values between slices using the same field mapping rules as struct-to-struct copying.
- Slice and Map Copiers - Copies values between slices or maps with automatic type conversion for compatible types.
- Slice and Map Type Converters - Converts between compatible slice and map types automatically during copy operations.
- Zero-Value Field Skippers - Filters out zero-value source fields to avoid overwriting destination data with empty values.
- Type Coercion Utilities - Automatically converts between compatible slice and map types during copy operations.
- Development Utilities - Copies values between structs.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
