Matthias Als

The documentation looks correct to me. Overriding uses this example: https://github.com/lidatong/dataclasses-json/blob/4a24b1261ee55e876c56665d72501f303e62f5c4/README.md?plain=1#L498-L512 And extending uses this example: https://github.com/lidatong/dataclasses-json/blob/4a24b1261ee55e876c56665d72501f303e62f5c4/README.md?plain=1#L520-L533 They are different ways of achieving the same behaviour.

I see, then I am unsure how the docs are updated. Maybe @lidatong can hint how to do so?

Also, please sync your branch to latest master commit. Then we can proceed with a merge

This is fixed by https://github.com/lidatong/dataclasses-json/issues/432 / https://github.com/lidatong/dataclasses-json/pull/434.

Maybe related to https://github.com/lidatong/dataclasses-json/pull/389

Closing due to lack of details. Maybe related to https://github.com/lidatong/dataclasses-json/issues/232. Please reopen if the issue persists or if you can provide more details.

Thanks for your PR. Imo, I believe dataclasses-json should only support native types out of the box while 3rd-party types like numpy can be de/encoded with custom encoders.

Closing this in favor of #470

I tested this in Python 3.8 / dataclasses-json newest version on master, and this code runs just fine. Closing issue, but if it reappears, please reopen this issue with more...

I was not able to recreate any issues from above information. Can you confirm it is still an issue and provide information such as dataclasses-json version, python version, etc., as...