[FEAT] Encoding Interfaces

[bbengfort]

Scope of changes

Adds the encoding.TextMarshaler and encoding.BinaryMarshaler interfaces.

Estimated PR Size:

• Tiny
• Small
• Medium
• Large
• Huge

Acceptance criteria

This PR will be merged without review.

Author checklist

• I have manually tested the change and/or added automation in the form of unit tests or integration tests
• I have updated the dependencies list
• I have added new test fixtures as needed to support added tests
• I have added or updated the documentation
• I have run go generate to update generated code

---

Note

Medium Risk
Adds new generated MarshalText/UnmarshalText and MarshalBinary/UnmarshalBinary methods and expands parsing of []byte inputs, which can change serialization/deserialization behavior for existing enums.

Overview
Generated enums now optionally implement encoding text and binary marshaling interfaces via new MarshalText/UnmarshalText and MarshalBinary/UnmarshalBinary methods (gated by NoText/NoBinary options).

ParseFactory is extended to handle []byte inputs by treating multi-byte slices as strings and single-byte slices as numeric values, with corresponding unit test coverage added for byte and byte-slice cases.

^{Reviewed by Cursor Bugbot for commit 9dccb90. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9dccb90. Configure here.}

[cursor]

Single-byte slice parsing skips range validation

High Severity

The case []byte handler for single-byte slices returns T(v[0]) without validating the value against the enum's defined range. This differs from other numeric type handlers, which correctly check bounds and return an error for out-of-range values.

 

^{Reviewed by Cursor Bugbot for commit 9dccb90. Configure here.}

[cursor]

Generated UnmarshalBinary accepts out-of-range byte values

High Severity

The UnmarshalBinary method, when handling single-byte input, directly casts the byte to the enum type. This bypasses the validation logic used by other unmarshalers, allowing invalid byte values to create invalid enum instances.

 

^{Reviewed by Cursor Bugbot for commit 9dccb90. Configure here.}