Oxan van Leeuwen

This has now been merged into master.

Hi! Sorry for the silence, I've neglected this project quite a bit over the last year. Tonight I've finished refactoring the component to use ESPHome's socket abstraction (see #25). During...

Equivalent functionality has been merged with #25.

> > The following two patches made it work. I think the first one is a bug as it detects wrongly `int | str | None` as an `Optional[int]`. >...

> Main motivation was that it seems Debian's next release (Bookworm) later this year will remain on `postsrsd` 1.10, and that also appears to be the same version in their...

I'm not sure if suppressing the autogeneration of a field if another field uses it as `source` would be a sensible default. I can imagine usecases where `source` is used...

> From what I see, to make those dataclasses work with serializers, I would have to subclass the UnionField, override `get_discriminator` and explicitly define this on my serializer: Defining your...

> If you create dataclasses to model an existing protocol, you run into some issues. That doesn't surprise me, as it's not a common usecase. > They simply try to...

> Hi, what are the concerns with using `Literal`? I don't like that it creates an extra field on the dataclass, which mixes actual data with metadata. It also allows...