Designing functional and fluent API: example of the Visitor Pattern by José Paumard

[@666KING6666]

Absolutely bonkers! Love it and hate it at the same time. Thankfully, starting with Java21 and type-pattern matching visitors can be replaced with switch expressions. Additionally, if sealed classes/interfaces are used, it can offer a compile-time guarantee that all subtypes in the hierarchy have been properly taken care of. Unlike here, where visiting logic is placed in the registry and only breaks at run-time. And with NPE, of all things! Nonetheless, video offers a lot of neat tricks for functional and fluent APIs. I'll surely use them either for builders or custom assertion classes for AssertJ.

[@ruixue6955]

1:30 why Visitor Pattern 3:28 code demo 3:37 the Visitor Pattern has to visit some *graph* object

[@andreidei]

this talk should be entitled "insane people code like this"...

[@justADeni]

it got pretty good in the middle and then devolved again in the end

[@badpotato]

this is Nice video. it is a different way of solving a problem

[@kitkarson4226]

Great presentation.

[@leonidpiliptsevich5329]

Awesome, thank you!

[@TJ-hs1qm]

9:06 vp violates the GOF rule to never depend on concrete types, only on abstractions. How do you inject MockBody for Body in a test if the code depends on concrete types?

[@mihaiapostol7864]

use mockito

[@hemanhy]

Very insightful Thank you!

[@nithinvarghese4737]

Great Video Learned a lot and a lot of tricks are now in my sleeve !! . Thank you soo much 34:52 In the Interface X, How can one call define method type() as an instance value out of it , Can anyone share info or notes on the same?

[@kitkarson4226]

check at 33:44 - type() is a method in the interface X

[@yadigarcaliskan6453]

Great thank you!

[@an2ber]

i hope nobody writes this kind of code in production

[@kitkarson4226]

It is about learning various tricks. You do not have to write like this. sometimes, to teach, we have to use things like this.