Return to Answer

@Data will turn your class into a full fledged DTO. Rather then simply letting you make your private members public it also implements toString, equals, and hash. Since you're not building a polymorphic encapsulated behavior object anyway you might as well add all the @Bells and @Whistles.

Yes it sticks you with a constructor you don't need thanks to those setters and lets anyone fiddle with it's data at any time but hey, you only live once. Some people insist on only adding what you really need. But they're no fun.

That might read as sarcasm but seriously it sounds like this codebase already doesn't care about ISP. Pick your fights wisely.

@Data will turn your class into a full fledged DTO. Rather then simply letting you make your private members public it also implements toString, equals, and hash. Since you're not building a polymorphic encapsulated behavior object anyway you might as well add all the @Bells and @Whistles.

Yes it sticks you with a constructor you don't need, and thanks to those setters, lets anyone fiddle with it's data at any time but hey, you only live once. Some people insist on only adding what you really need. But they're no fun.

That might read as sarcasm but seriously it sounds like this codebase already doesn't care about ISP. Pick your fights wisely.

@Data will turn your class into a full fledged DTO. Rather then simply letting you make your private members public it also implements toString, equals, and hash. Since you're not building a polymorphic encapsulated behavior object anyway you might as well add all the @Bells and @Whistles.

Yes it sticks you with a constructor you don't need thanks to those setters and lets anyone fiddle with it's data at any time but hey, you only live once. Some people insist on only adding what you really need. But they're no fun.

This might read as sarcasm but seriously it sounds like this codebase already doesn't care about ISP. Pick your fights wisely.

@Data will turn your class into a full fledged DTO. Rather then simply letting you make your private members public it also implements toString, equals, and hash. Since you're not building a polymorphic encapsulated behavior object anyway you might as well add all the @Bells and @Whistles.

Yes it sticks you with a constructor you don't need thanks to those setters and lets anyone fiddle with it's data at any time but hey, you only live once. Some people insist on only adding what you really need. But they're no fun.

That might read as sarcasm but seriously it sounds like this codebase already doesn't care about ISP. Pick your fights wisely.

@Data will turn your class into a full fledged DTO. Rather then simply letting you make your private members public it also implements toString and hash. Since you're not building a polymorphic encapsulated behavior object anyway you might as well add all the @Bells and @Whistles.

@Data will turn your class into a full fledged DTO. Rather then simply letting you make your private members public it also implements toString, equals, and hash. Since you're not building a polymorphic encapsulated behavior object anyway you might as well add all the @Bells and @Whistles.

Yes it sticks you with a constructor you don't need thanks to those setters and lets anyone fiddle with it's data at any time but hey, you only live once. Some people insist on only adding what you really need. But they're no fun.

This might read as sarcasm but seriously it sounds like this codebase already doesn't care about ISP. Pick your fights wisely.