When using the Decorator pattern, how do you decorate additional functionality in between the concrete...












0















I'm trying to understand if I am using the Decorator pattern properly, or if another pattern would be better suited for a situation like this:



Without redefining my interface, I am unable to decorate a function because it's parent's definition prevents me from doing so. I'm not sure if my question is clear, so perhaps an example:



interface IFoo
{
public function bar();
}

class ConcreteFoo implements IFoo
{
public function bar()
{
echo "hello world!n";
}
}

abstract class Decorator implements IFoo
{
public function __construct(IFoo $foo)
{
$this->foo = $foo;
}

public function bar()
{
$this->foo->bar();
}
}

class BeautifulDecorator extends Decorator
{
public function bar()
{
// I am unable to insert 'beautiful' between 'hello' and 'world' without redefining the bar() function again
parent::bar();
}
}


For the sake of simplicity, I am essentially unable to print out something like 'hello beautiful world' without actually redefining the bar function to do so.



Is there a way to do so with the Decorator pattern, or is there a different pattern that can be used?










share|improve this question























  • A decorator "wraps" the decoratee and can add functionality before/after the wrapped methods - to inject functionality you would need to use something like the strategy pattern

    – qujck
    Nov 16 '18 at 8:44
















0















I'm trying to understand if I am using the Decorator pattern properly, or if another pattern would be better suited for a situation like this:



Without redefining my interface, I am unable to decorate a function because it's parent's definition prevents me from doing so. I'm not sure if my question is clear, so perhaps an example:



interface IFoo
{
public function bar();
}

class ConcreteFoo implements IFoo
{
public function bar()
{
echo "hello world!n";
}
}

abstract class Decorator implements IFoo
{
public function __construct(IFoo $foo)
{
$this->foo = $foo;
}

public function bar()
{
$this->foo->bar();
}
}

class BeautifulDecorator extends Decorator
{
public function bar()
{
// I am unable to insert 'beautiful' between 'hello' and 'world' without redefining the bar() function again
parent::bar();
}
}


For the sake of simplicity, I am essentially unable to print out something like 'hello beautiful world' without actually redefining the bar function to do so.



Is there a way to do so with the Decorator pattern, or is there a different pattern that can be used?










share|improve this question























  • A decorator "wraps" the decoratee and can add functionality before/after the wrapped methods - to inject functionality you would need to use something like the strategy pattern

    – qujck
    Nov 16 '18 at 8:44














0












0








0


1






I'm trying to understand if I am using the Decorator pattern properly, or if another pattern would be better suited for a situation like this:



Without redefining my interface, I am unable to decorate a function because it's parent's definition prevents me from doing so. I'm not sure if my question is clear, so perhaps an example:



interface IFoo
{
public function bar();
}

class ConcreteFoo implements IFoo
{
public function bar()
{
echo "hello world!n";
}
}

abstract class Decorator implements IFoo
{
public function __construct(IFoo $foo)
{
$this->foo = $foo;
}

public function bar()
{
$this->foo->bar();
}
}

class BeautifulDecorator extends Decorator
{
public function bar()
{
// I am unable to insert 'beautiful' between 'hello' and 'world' without redefining the bar() function again
parent::bar();
}
}


For the sake of simplicity, I am essentially unable to print out something like 'hello beautiful world' without actually redefining the bar function to do so.



Is there a way to do so with the Decorator pattern, or is there a different pattern that can be used?










share|improve this question














I'm trying to understand if I am using the Decorator pattern properly, or if another pattern would be better suited for a situation like this:



Without redefining my interface, I am unable to decorate a function because it's parent's definition prevents me from doing so. I'm not sure if my question is clear, so perhaps an example:



interface IFoo
{
public function bar();
}

class ConcreteFoo implements IFoo
{
public function bar()
{
echo "hello world!n";
}
}

abstract class Decorator implements IFoo
{
public function __construct(IFoo $foo)
{
$this->foo = $foo;
}

public function bar()
{
$this->foo->bar();
}
}

class BeautifulDecorator extends Decorator
{
public function bar()
{
// I am unable to insert 'beautiful' between 'hello' and 'world' without redefining the bar() function again
parent::bar();
}
}


For the sake of simplicity, I am essentially unable to print out something like 'hello beautiful world' without actually redefining the bar function to do so.



Is there a way to do so with the Decorator pattern, or is there a different pattern that can be used?







design-patterns decorator






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '18 at 8:12









kennzorskennzors

107




107













  • A decorator "wraps" the decoratee and can add functionality before/after the wrapped methods - to inject functionality you would need to use something like the strategy pattern

    – qujck
    Nov 16 '18 at 8:44



















  • A decorator "wraps" the decoratee and can add functionality before/after the wrapped methods - to inject functionality you would need to use something like the strategy pattern

    – qujck
    Nov 16 '18 at 8:44

















A decorator "wraps" the decoratee and can add functionality before/after the wrapped methods - to inject functionality you would need to use something like the strategy pattern

– qujck
Nov 16 '18 at 8:44





A decorator "wraps" the decoratee and can add functionality before/after the wrapped methods - to inject functionality you would need to use something like the strategy pattern

– qujck
Nov 16 '18 at 8:44












1 Answer
1






active

oldest

votes


















0














Use Decorator when




  • you want the object to perform additional operations before and after the execution of a method


  • extension by subclassing can lead to an explosion of subclasses to support every combination of operations



In your case, you do not want to add any additional operations before or after the bar() but you actually want to replace the algorithm of that method, so this is not the intent of Decorator



And if the class prevents you from changing its algorithm, in your example, there're no ways to ask the object to print anything other than 'hello world!', so that means the behavior is encapsulated into the object and there are no patterns designed to break the encapsulation.



I believe the only solution here is change the ConcreteFoo implementation or just create another concrete class.






share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53333816%2fwhen-using-the-decorator-pattern-how-do-you-decorate-additional-functionality-i%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Use Decorator when




    • you want the object to perform additional operations before and after the execution of a method


    • extension by subclassing can lead to an explosion of subclasses to support every combination of operations



    In your case, you do not want to add any additional operations before or after the bar() but you actually want to replace the algorithm of that method, so this is not the intent of Decorator



    And if the class prevents you from changing its algorithm, in your example, there're no ways to ask the object to print anything other than 'hello world!', so that means the behavior is encapsulated into the object and there are no patterns designed to break the encapsulation.



    I believe the only solution here is change the ConcreteFoo implementation or just create another concrete class.






    share|improve this answer






























      0














      Use Decorator when




      • you want the object to perform additional operations before and after the execution of a method


      • extension by subclassing can lead to an explosion of subclasses to support every combination of operations



      In your case, you do not want to add any additional operations before or after the bar() but you actually want to replace the algorithm of that method, so this is not the intent of Decorator



      And if the class prevents you from changing its algorithm, in your example, there're no ways to ask the object to print anything other than 'hello world!', so that means the behavior is encapsulated into the object and there are no patterns designed to break the encapsulation.



      I believe the only solution here is change the ConcreteFoo implementation or just create another concrete class.






      share|improve this answer




























        0












        0








        0







        Use Decorator when




        • you want the object to perform additional operations before and after the execution of a method


        • extension by subclassing can lead to an explosion of subclasses to support every combination of operations



        In your case, you do not want to add any additional operations before or after the bar() but you actually want to replace the algorithm of that method, so this is not the intent of Decorator



        And if the class prevents you from changing its algorithm, in your example, there're no ways to ask the object to print anything other than 'hello world!', so that means the behavior is encapsulated into the object and there are no patterns designed to break the encapsulation.



        I believe the only solution here is change the ConcreteFoo implementation or just create another concrete class.






        share|improve this answer















        Use Decorator when




        • you want the object to perform additional operations before and after the execution of a method


        • extension by subclassing can lead to an explosion of subclasses to support every combination of operations



        In your case, you do not want to add any additional operations before or after the bar() but you actually want to replace the algorithm of that method, so this is not the intent of Decorator



        And if the class prevents you from changing its algorithm, in your example, there're no ways to ask the object to print anything other than 'hello world!', so that means the behavior is encapsulated into the object and there are no patterns designed to break the encapsulation.



        I believe the only solution here is change the ConcreteFoo implementation or just create another concrete class.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 18 '18 at 18:17

























        answered Nov 18 '18 at 18:09









        ndnhuyndnhuy

        912




        912






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53333816%2fwhen-using-the-decorator-pattern-how-do-you-decorate-additional-functionality-i%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            這個網誌中的熱門文章

            Xamarin.form Move up view when keyboard appear

            Post-Redirect-Get with Spring WebFlux and Thymeleaf

            Anylogic : not able to use stopDelay()