Description

The issue raised concerns about binding integer values from frontend requests to pointer types like *int64 in Fiber v3. Testing confirms this functionality works correctly. However, the test suite lacked coverage for pointer scalar types, making it difficult to verify behavior and prevent regressions.

This PR adds comprehensive test coverage demonstrating that binding to pointer scalar types works as expected in Fiber v3, including tests for the specific use-case from the original issue across all binder types (Query, Form, and JSON).

Changes introduced

• Test Coverage: Added comprehensive tests covering:
  • Test_QueryBinder_Bind_PointerScalars and Test_FormBinder_Bind_PointerScalars covering *int64, *string, *bool, *float64
  • All fields provided: pointers are non-nil with correct values
  • No fields provided: pointers remain nil (vs zero values for non-pointers)
  • Partial fields: only provided fields have non-nil pointers
  • Explicit zero/empty values provided (id=0&name=&active=false&score=0): pointers are non-nil with correct zero values, distinguishing "explicitly sent zero" from "not sent at all"
  • Test_QueryBinder_Bind_OptionalIDParam, Test_FormBinder_Bind_OptionalIDParam, and Test_JSON_Binding_Bind_OptionalIDParam testing the exact use-case from the original issue with OptionalIDParam struct containing IDPtr *int64 with appropriate struct tags (query, form, and json)

Example usage:

// Query/Form binding
type Query struct {
    ID     *int64  `query:"id"`
    Name   *string `query:"name"`
    Active *bool   `query:"active"`
}

// JSON binding (from original issue)
type OptionalIDParam struct {
    IDPtr *int64 `json:"id"`
}

// When ?id=123&name=test is sent:
// - ID is non-nil with value 123
// - Name is non-nil with value "test"
// - Active is nil (not provided)

// When ?id=0&name= is sent:
// - ID is non-nil with value 0
// - Name is non-nil with value ""
// - Active is nil (not provided)

// When {"id":null} is sent in JSON:
// - IDPtr is nil (explicit null)

// vs non-pointer int64 which would be 0 when not provided

The key advantage: pointer types distinguish between "not sent" (nil) and "zero value" (0, "", false).

• Benchmarks: N/A - test-only change
• Documentation Update: N/A - behavior already supported
• Changelog/What's New: N/A - test-only change
• Migration Guide: N/A - no API changes
• API Alignment with Express: N/A
• API Longevity: Test coverage ensures stability
• Examples: Test cases serve as examples

Type of change

• New feature (non-breaking change which adds functionality)
• Enhancement (improvement to existing features and functionality)
• Documentation update (changes to documentation)
• Performance improvement (non-breaking change which improves efficiency)
• Code consistency (non-breaking change which improves code reliability and robustness)

Checklist

Before you submit your pull request, please make sure you meet these requirements:

• Followed the inspiration of the Express.js framework for new functionalities, making them similar in usage.
• Conducted a self-review of the code and provided comments for complex or critical parts.
• Updated the documentation in the /docs/ directory for Fiber's documentation.
• Added or updated unit tests to validate the effectiveness of the changes or new features.
• Ensured that new and existing unit tests pass locally with the changes.
• Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
• Aimed for optimal performance with minimal allocations in the new code.
• Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Please use emojis in commit messages for an easy way to identify the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md