How to handle JSON requests and responses with go-dry?

Use HTTPRespondMarshalJSON for compressed JSON responses and HTTPUnmarshalRequestBodyJSON for parsing request bodies. These helpers simplify web server development by integrating compression and marshaling in one call.

go-dry vs standard Go libraries for file operations?

go-dry adds convenience with functions like FileCopyDir and FileGetNonEmptyLines, but the standard library offers more control and explicit error handling. Choose go-dry for rapid development where boilerplate reduction is key.

Is go-dry's SyncMap thread-safe for concurrent use?

Yes, SyncMap provides thread-safe operations for maps, as documented with methods like AddString. It wraps synchronization internally, making it easier to manage shared data in goroutines.

How to migrate from go-quick to go-dry?

The README notes that go-dry replaces go-quick, so update imports and check for API changes. Review the documentation for equivalent functions, as some signatures or behaviors might have been updated.

Best practices for using go-dry ErrorList in projects?

Use ErrorList to collect errors from multiple operations, then check Err() at the end. It's ideal for batch processing, but for critical errors, consider standard error propagation to avoid masking issues.

Does go-dry support secure AES encryption?

It provides AES encryption/decryption with cipher block pooling, but always validate inputs and follow security best practices externally, as the README cautions against relying on its hash functions for cryptography.

go-dry — Go Utility Package for Boilerplate

What is go-dry?

go-dry is a Go utility library that provides a comprehensive collection of helper functions and types to eliminate repetitive boilerplate code in Go applications. It offers utilities for common tasks like string manipulation, file I/O, HTTP handling, error management, concurrency, and encryption, enabling developers to write more concise and consistent code. The library adheres to the DRY (Don't Repeat Yourself) principle, aiming to reduce redundancy and accelerate development.

Target Audience

Go developers working on applications that involve frequent string processing, file operations, web server development, or concurrent data handling, and who seek to minimize boilerplate code. It is particularly useful for backend developers building web services, CLI tools, or systems requiring utilities for JSON/XML marshaling, encryption, and thread-safe operations.

Value Proposition

Developers choose go-dry for its extensive, all-in-one set of utilities that cover a wide range of common Go programming patterns, reducing the need to write or import multiple specialized packages. Its unique selling point is the integration of thread-safe types, error collection with ErrorList, and performance optimizations like compression pools, which streamline development while maintaining consistency across projects.

DRY (don't repeat yourself) package for Go

Use Cases

Best For

Building web servers in Go that require HTTP utilities for JSON/XML marshaling, compression, and request handling.
Developing CLI tools or scripts that need robust file I/O operations for reading/writing JSON, XML, CSV, or config files.
Implementing concurrent applications where thread-safe wrappers for primitives (e.g., SyncInt, SyncMap) are necessary to manage shared state.
Reducing boilerplate code in Go projects by using utilities for string parsing, conversion, and transformation (e.g., StringToInt, StringFindBetween).
Handling error collection and debugging with features like ErrorList for multiple errors and panic helpers with stack traces.
Performing encryption and byte operations, such as AES encryption/decryption with pooling or compression for byte slices.

Not Ideal For

Projects that prioritize minimal dependencies and stick strictly to the Go standard library to avoid third-party packages.
Security-critical applications requiring audited cryptographic implementations, given go-dry's warnings against using its hash functions for security purposes.
Teams that prefer specialized, single-purpose libraries for better maintenance and updates, as go-dry's broad scope can introduce unnecessary complexity.
Situations where explicit error handling is essential, since functions like StringToInt return zero values on errors instead of propagating errors.

Pros & Cons

Pros

Comprehensive Utility Coverage

Offers a wide range of helpers for strings, files, HTTP, errors, and more, such as StringFindBetween for text extraction and FileUnmarshallJSON for easy file parsing, reducing repetitive code.

Thread-Safe Concurrency Types

Includes SyncInt, SyncMap, and other wrappers that simplify shared state management in concurrent applications without manual mutex handling, as shown in the thread-safe examples.

Efficient Error Collection

Features ErrorList for accumulating multiple errors and PanicIfErr with stack traces, making debugging easier and error handling more organized in complex operations.

Performance Optimizations

Implements compression pools like Gzip.GetWriter for resource reuse, optimizing throughput in data-intensive scenarios like HTTP response handling.

Cons

Security Caveats

The README explicitly warns that MD5 and SHA1 functions are for non-cryptographic use only, and input validation in utilities like StringToInt may silently fail by returning zero values, hiding errors in production code.

Dependency Overhead

As a monolithic utility package, it can introduce bloat and potential conflicts with other libraries, especially if only a subset of features is needed, increasing project complexity.

Error Handling Abstraction

Functions that abstract error checking, such as returning zero values on parse errors, might encourage poor practices if developers overlook the warnings, leading to less robust applications.

What is go-dry?

Target Audience

Value Proposition

Use Cases

Best For

Building web servers in Go that require HTTP utilities for JSON/XML marshaling, compression, and request handling.
Developing CLI tools or scripts that need robust file I/O operations for reading/writing JSON, XML, CSV, or config files.
Implementing concurrent applications where thread-safe wrappers for primitives (e.g., SyncInt, SyncMap) are necessary to manage shared state.
Reducing boilerplate code in Go projects by using utilities for string parsing, conversion, and transformation (e.g., StringToInt, StringFindBetween).
Handling error collection and debugging with features like ErrorList for multiple errors and panic helpers with stack traces.
Performing encryption and byte operations, such as AES encryption/decryption with pooling or compression for byte slices.

Not Ideal For

Projects that prioritize minimal dependencies and stick strictly to the Go standard library to avoid third-party packages.
Security-critical applications requiring audited cryptographic implementations, given go-dry's warnings against using its hash functions for security purposes.
Teams that prefer specialized, single-purpose libraries for better maintenance and updates, as go-dry's broad scope can introduce unnecessary complexity.
Situations where explicit error handling is essential, since functions like StringToInt return zero values on errors instead of propagating errors.

Pros & Cons

Pros

Comprehensive Utility Coverage

Offers a wide range of helpers for strings, files, HTTP, errors, and more, such as StringFindBetween for text extraction and FileUnmarshallJSON for easy file parsing, reducing repetitive code.

Thread-Safe Concurrency Types

Includes SyncInt, SyncMap, and other wrappers that simplify shared state management in concurrent applications without manual mutex handling, as shown in the thread-safe examples.

Efficient Error Collection

Features ErrorList for accumulating multiple errors and PanicIfErr with stack traces, making debugging easier and error handling more organized in complex operations.

Performance Optimizations

Implements compression pools like Gzip.GetWriter for resource reuse, optimizing throughput in data-intensive scenarios like HTTP response handling.

Cons

Security Caveats

Dependency Overhead

As a monolithic utility package, it can introduce bloat and potential conflicts with other libraries, especially if only a subset of features is needed, increasing project complexity.

Error Handling Abstraction

Functions that abstract error checking, such as returning zero values on parse errors, might encourage poor practices if developers overlook the warnings, leading to less robust applications.

go-dry

What is go-dry?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

go-dry

What is go-dry?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?