Yikes 👀 . Been punting on this one for a while now...

Aside @auvipy: Probably better to refrain from pitching in asking contributors to rebase, particularly given that the ticket's remained inactive for so long.

It's not entirely clear to me what the behaviour should be where a nested serialiser has a list of errors rather than a dictionary, but it probably shouldn't be to error out.

That seems right, but we still need to settle what the appropriate response is here.

I'm going to de-milestone for now.

It looks like this has been fixed at some point. Is it worth it to clean up the test case (eg, check what the expected behavior should be, instead of just not failing) and add it to the test suite?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

It looks like this has been fixed at some point. Is it worth it to clean up the test case (eg, check what the expected behavior should be, instead of just not failing) and add it to the test suite?

that would be the right approach FMPOV. also the test seems to have lots of conflicts to resolve. I will try to investigate and try this test freshly

that would be the right approach FMPOV. also the test seems to have lots of conflicts to resolve. I will try to investigate and try this test freshly

Why make work?