fix: respect Binder interface for primitive types in BindStringToObject #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the Binder interface was only checked within the struct case of the type switch, causing primitive types (strings, ints, etc.) that implement Binder to bypass their custom binding logic. This fix moves the Binder check to the beginning of BindStringToObject, ensuring all types implementing Binder use their custom Bind method, regardless of their underlying type. The redundant check in the struct case has been removed.