Closed xenoterracide closed 1 year ago
I've tried reading this issue several times now and given up each time, because I simply have no idea what's going on here. I don't know Kotlin, and I don't have a lot of spare time. Please write a proper description and use the prompts provided when you open a new ticket, they're there for a reason...
Identifiable is an interface that requires an id field, these classes that are provided in the test can be simple extensions of this code otherwise. Kotlin does magic garbage. In order to test this though you have to set up kotlin. An essentially extend a class with a field I'd. Then try to use that method as documented. It blows up in very strange ways. Most likely because the internals of kotlin don't work like Java would.
I was finally able to find some time to work on EqualsVerifier (my employer graciously donated some time), but I still don't understand what you're getting at, unfortunately. My spare time is very precious to me, and if I have to choose between hacking on EqualsVerifier or trying to parse unclear issue reports, I think you can guess which I'll choose. So I'm going to close this issue.
Of course you're free to open a new issue about this if you want, but if you do, take a good look at the questions in the issue template, and answer each one of them individually. You often ignore them, but they're there for a good reason, i.e., saving me time.
I really want to help you, but if you don't answer the questions in the template, I don't know how. Also, in this case, I will require a small demo project (either as a zip file or as a separate GitHub repo) that reproduces the issue, because otherwise I won't be able to reproduce the problem.
If you do all of that I still can't promise I can help you quickly (my time for EqualsVerifier is still extremely limited), but at least you'll have a much better chance...
Eh, I'm back to not doing kotlin anyways. Although I don't feel like this was a bad report because I did include code samples. But I'm pretty meh about it at the moment.
Indeed, there are code samples, but I still don't understand what the actual problem is. I could probably figure it out, but it would take me at least several hours to do so (remember that I don't know Kotlin, so I have no clear handle on what is expected there and what isn't).
Anyway, don't hesitate to re-submit this issue if you ever do return to Kotlin, but please do answer the questions from the template if you do!
Is your feature request related to a problem? Please describe.
Kotlin is weird with its magical property nonsense. My guess is the field is missing, but not the getter/setter. If that's what's happening then what might be best is to be able to write
withOnlyTheseProperties("id")
and have it also look for getters/setters.nl.jqno.equalsverifier:equalsverifier:3.10.1