From 221daf5d7495faf161bab0463681edd92adc0224 Mon Sep 17 00:00:00 2001 From: Anum Amin <39243539+blueberry404@users.noreply.github.com> Date: Sun, 24 Oct 2021 11:03:29 +0500 Subject: [PATCH] docs: Add tutorial links for Visitor pattern (#525) (#1880) --- visitor/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/visitor/README.md b/visitor/README.md index 82176238f..38df87d28 100644 --- a/visitor/README.md +++ b/visitor/README.md @@ -214,6 +214,12 @@ Use the Visitor pattern when * Many distinct and unrelated operations need to be performed on objects in an object structure, and you want to avoid "polluting" their classes with these operations. Visitor lets you keep related operations together by defining them in one class. When the object structure is shared by many applications, use Visitor to put operations in just those applications that need them. * The classes defining the object structure rarely change, but you often want to define new operations over the structure. Changing the object structure classes requires redefining the interface to all visitors, which is potentially costly. If the object structure classes change often, then it's probably better to define the operations in those classes. +## Tutorials + +* [Refactoring Guru](https://refactoring.guru/design-patterns/visitor) +* [Dzone](https://dzone.com/articles/design-patterns-visitor) +* [Sourcemaking](https://sourcemaking.com/design_patterns/visitor) + ## Known uses * [Apache Wicket](https://github.com/apache/wicket) component tree, see [MarkupContainer](https://github.com/apache/wicket/blob/b60ec64d0b50a611a9549809c9ab216f0ffa3ae3/wicket-core/src/main/java/org/apache/wicket/MarkupContainer.java)