Jakob Kogler

@mgalindor Thanks for the idea. However I don't think that I will implement it like you suggested. One of the fundamental ideas of this library was, to make mappers safe...

Will be implemented with #25

Available in [v2.0.0a0](https://github.com/dataclass-mapper/dataclass-mapper/releases/tag/v2.0.0a0)

Quite hard to implement this. There are quite a lot of different types of validators (e.g. a type can have multiple validators, a validator can be valid for every field,...

Follow up from #10 @filwaline Btw, circular dataclasses are quite dangerous and complicated. E.g. ```python from pydantic import BaseModel class Book(BaseModel): name: str author: "Author" class Author(BaseModel): name: str books:...

I'm not opposed to this idea. But I'm not completely sure how it would look like for nested conversions. On of the nicer features of the global registration is, that...

I'll think about it in the next few days. Another advantage is, that by having a mapper instance, you guarantee that the mapper was actually created. Currently, if you define...

I also thought about the problem of defining multiple mappings between two classes before. I had planned to create something like mapper instances, however more in the sense of mapping...

I kinda prefer the original message, because the error is more specific. Not only does the library not know, how to convert between the two types, it doesn't even understand...

Yes, we use Google Analytics. Looks like the usage is very stable (but definitely also not growing).  @adamant-pwn @mhayter I've invited you both to the Google Analytics page: https://analytics.google.com/analytics/web/#/p380863626/reports/intelligenthome...