Modified ManufacturerDataField to return a namedtuple if possible #116
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.
I'm definitely not convinced this covers all cases, nor am I convinced it's non-breaking, so I'm interested in feedback (but it does work neatly in my case).
If a given
Advertisement
subclass is defined with multiple fields in a singleManufacturerDataField
, the current class requires it to have an array offield_names
, which heretofore are unused.This PR 1) enforces that
field_names
must be formatted properly for a namedtuple (i.e. no spaces, probably plenty of other things) and 2) returns aMDFTuple
instead of a regular tuple, with fields named as defined.Mostly, I'm not sure when lines 285+ come into play, and whether they ought to be covered by the namedtuple modification.