ChoiceWrapper was not behaving correctly with regard to detecting the value because the nested choices value was not force_texted. I added the check in the test case for bound forms.
As a side effect, it turned out that building ChoiceWrapper as a simple namedtuple was not flexible enough, so I made it a proper object that quacks like a tuple.
Version bump + pypi release would be appropriate :-)
Coverage increased (+0.8%) to 73.031% when pulling 982be73d590d439b7fd50e77e6a13ede1e45a40f on sergei-maertens:feature/django-widgets-library into 8e654e8a89367fccec7ac086e4186a917362c867 on funkybob:master.
ChoiceWrapper was not behaving correctly with regard to detecting the value because the nested choices value was not
force_text
ed. I added the check in the test case for bound forms.As a side effect, it turned out that building
ChoiceWrapper
as a simplenamedtuple
was not flexible enough, so I made it a proper object that quacks like a tuple.Version bump + pypi release would be appropriate :-)