Hello, I stumbled upon a bug, where Optional<List> as field is manufactured as Optional<List
I know that Optional as a field is a bad practice but actually, I wrote for my purposes a similar to Optional generic class and found this bug with podam and I changed class to Optional for clarity.
Hello, I stumbled upon a bug, where Optional<List> as field is manufactured as Optional<List
I know that Optional as a field is a bad practice but actually, I wrote for my purposes a similar to Optional generic class and found this bug with podam and I changed class to Optional for clarity.