Fix an issue introduced with hetero tuple decode

[george-zubrienko]

Fixes #491

I believe one way to fix this is to simply narrow down use cases for hetero tuples to either types == elements in tuple, or a single type :)

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
dataclasses_json
cfg.py	51	4	92%	80, 84–86
core.py	260	18	93%	39–42, 52, 65, 67, 82, 84, 170, 198, 378–385, 389, 395
mm.py	205	30	85%	33–36, 42–45, 53–56, 62–65, 88, 170–171, 176, 180, 184, 189, 193, 197, 205, 211, 216, 225, 230, 235, 244, 253–260
stringcase.py	25	3	88%	59, 76, 97
undefined.py	146	2	99%	25, 39
utils.py	131	36	73%	12–25, 45–50, 61–65, 75, 100–101, 109–110, 125–133, 163, 182, 207
tests
entities.py	239	3	99%	22, 234, 240
test_annotations.py	81	42	48%	50–67, 78–102, 106–122
test_api.py	142	4	97%	88, 99, 139–140
test_str_subclass.py	22	1	95%	9
test_union.py	131	10	92%	97–104, 118–125
TOTAL	2647	153	94%

Tests	Skipped	Failures	Errors	Time
305	3 💤	0 ❌	0 🔥	6.525s ⏱️

[matt035343]

@george-zubrienko Actually, in the referenced issue, the type hint does not match the actual value of the field/variable. Let me quote the Python doc, Annotating Tuples

# OK: ``x`` is assigned to a tuple of length 1 where the sole element is an int
x: tuple[int] = (5,)

# OK: ``y`` is assigned to a tuple of length 2;
# element 1 is an int, element 2 is a str
y: tuple[int, str] = (5, "foo")

# Error: the type annotation indicates a tuple of length 1,
# but ``z`` has been assigned to a tuple of length 3
z: tuple[int] = (1, 2, 3)

The latter case is what is described in the issue. I think raising an error for tuples where number of elements != number of type args would be appropriate.

[george-zubrienko]

@matt035343 so I just leave the if len(type_args) == len(xs): and remove the ==1 branch?

[matt035343]

@matt035343 so I just leave the if len(type_args) == len(xs): and remove the ==1 branch?

I guess that should do it. Btw, why did you opt for enumerate over zip? Is it performing better?