Regarding the organization of issues regarding value classes in jackson-module-kotlin.

[wrongwrong]

Currently, jackson-module-kotlin is creating a lot of issues about value class.
So, I would like to do the following work.

1. Create an issue for value class serialization support and an issue for deserialization support.

2. Close the existing issues related to the value class and merge them into the respective issues created in 1.

3. Describe in the issue template that "Please check if issues related to value class can be reproduced in jackson-module-kogera, and then create an issue there".

Since jackson-module-kogera is a private project, I am concerned that it would be a bad idea to write something that would advertise the project.

[Tatu Saloranta]

I think I agree with (1) and (2). But I think that adding a link to
private project from issue template would probably give the wrong idea
(and is probably not the right place for redirection in general) --
template should refer to issues created in (1) instead
("for Value-class related issues, see issues #aaa and #bbb to see if
they are already covered).

I have no objections if one or both issues from (1) had this note,
suggesting issue creation for Kogera project. As an additional thing
that may make sense.
So it would be slightly deeper in the issue path.

Does this make sense?

-+ Tatu +-

>
> --
> You received this message because you are subscribed to the Google Groups "jackson-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jackson-dev...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/109bed8c-d1b0-4271-91fc-3fccd139b084n%40googlegroups.com.

[宮田木織]

I understand.
I will respond when I have time.

2023年2月20日(月) 9:05 Tatu Saloranta <ta...@fasterxml.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/CAL4a10jrKoZ1FP-8HLk2788136%2B%2B5vaPz5Mp7ZnwM27gFLBcYA%40mail.gmail.com.