Use encoding.TextMarshaler/encoding.TextUnmarshaler if present #413
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.
Background:
In order to parse custom flag types it is currently necessary to implement the
flags.Unmarshaler
and optionally theflags.Marshaler
interface. That interface is specific to this library, but many types already make use ofencoding.TextMarshaler
andencoding.TextUnmarshaler
which is a bit more standardized. It is cumbersome, and sometimes impossible when you don't own the code, to implement both interfaces. Thus this PR allows adds the ability to marshal flags by those interfaces.Changes:
encoding.TextMarshaler
toconvertMarshal
only AFTER checking for theflags.Marshaler
interface.encoding.TextUnmarshaler
toconvertUnmarshal
only AFTER checking for theflags.Unmarshaler
interface.