Hi,
Thanks for the support. It looks like nobody objects to this proposal, so I
will start a formal vote.
Best,
Piotrek
pt., 21 paź 2022 o 08:24 Timo Walther napisał(a):
> Makes sense to me. The serializer stack is pretty complex right now, the
> more legacy we remove the better.
>
> Regards,
Makes sense to me. The serializer stack is pretty complex right now, the
more legacy we remove the better.
Regards,
Timo
On 20.10.22 12:49, Chesnay Schepler wrote:
+1
Sounds like a good reason to drop these long-deprecated APIs.
On 19/10/2022 15:13, Piotr Nowojski wrote:
Hi devs,
I would
+1
Sounds like a good reason to drop these long-deprecated APIs.
On 19/10/2022 15:13, Piotr Nowojski wrote:
Hi devs,
I would like to open a discussion to remove the long deprecated
(@PublicEvolving) TypeSerializerConfigSnapshot class [1] and the related
code.
The motivation behind this move
+1, I think that is a sensible think to do. I don't think this will
affect many users as those versions are already quite old.
As a side note, there is a different effort around serializers that
might introduce another incompatibility (in the API). I wonder if we
could squash it together
Hi devs,
I would like to open a discussion to remove the long deprecated
(@PublicEvolving) TypeSerializerConfigSnapshot class [1] and the related
code.
The motivation behind this move is two fold. One reason is that it
complicates our code base unnecessarily and creates confusion on how to
