When and how to choose between React Hooks and old HOC props passing?











up vote
3
down vote

favorite
1












Until now we were used to Flux flow where data entered into the component through props. So you could look at the Props signature and see what is the component requirements.



Hooks are an amazing feature, but as we transition to them I find that they provide another entrance for dependencies which is harder to manage since you have to look at the actual component code to see it.



Of course, we can use Hooks only in container components, but I feel that some of their main selling points are their ability to reduce nesting and HOC.



What are the best practices (currently) for deciding which component should use a hook and which should use render props?










share|improve this question






















  • which component should use a hook and which should use render props? - what case do you mean exactly?
    – estus
    Nov 20 at 7:30















up vote
3
down vote

favorite
1












Until now we were used to Flux flow where data entered into the component through props. So you could look at the Props signature and see what is the component requirements.



Hooks are an amazing feature, but as we transition to them I find that they provide another entrance for dependencies which is harder to manage since you have to look at the actual component code to see it.



Of course, we can use Hooks only in container components, but I feel that some of their main selling points are their ability to reduce nesting and HOC.



What are the best practices (currently) for deciding which component should use a hook and which should use render props?










share|improve this question






















  • which component should use a hook and which should use render props? - what case do you mean exactly?
    – estus
    Nov 20 at 7:30













up vote
3
down vote

favorite
1









up vote
3
down vote

favorite
1






1





Until now we were used to Flux flow where data entered into the component through props. So you could look at the Props signature and see what is the component requirements.



Hooks are an amazing feature, but as we transition to them I find that they provide another entrance for dependencies which is harder to manage since you have to look at the actual component code to see it.



Of course, we can use Hooks only in container components, but I feel that some of their main selling points are their ability to reduce nesting and HOC.



What are the best practices (currently) for deciding which component should use a hook and which should use render props?










share|improve this question













Until now we were used to Flux flow where data entered into the component through props. So you could look at the Props signature and see what is the component requirements.



Hooks are an amazing feature, but as we transition to them I find that they provide another entrance for dependencies which is harder to manage since you have to look at the actual component code to see it.



Of course, we can use Hooks only in container components, but I feel that some of their main selling points are their ability to reduce nesting and HOC.



What are the best practices (currently) for deciding which component should use a hook and which should use render props?







reactjs react-hooks






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 6:46









S.Kraus

109110




109110












  • which component should use a hook and which should use render props? - what case do you mean exactly?
    – estus
    Nov 20 at 7:30


















  • which component should use a hook and which should use render props? - what case do you mean exactly?
    – estus
    Nov 20 at 7:30
















which component should use a hook and which should use render props? - what case do you mean exactly?
– estus
Nov 20 at 7:30




which component should use a hook and which should use render props? - what case do you mean exactly?
– estus
Nov 20 at 7:30












1 Answer
1






active

oldest

votes

















up vote
1
down vote













Hooks are still in alpha and the devTools support is still in development for it. And according to the React FAQs hooks can be used as an alternative to renderProps and HOCs, but can coexist with them




Often, render props and higher-order components render only a single
child. We think Hooks are a simpler way to serve this use case. There
is still a place for both patterns
(for example, a virtual scroller
component might have a renderItem prop, or a visual container
component might have its own DOM structure). But in most cases, Hooks
will be sufficient and can help reduce nesting in your tree.




Hooks allow stateful logic in functional components and would be similar to class components in React.




Hooks are harder to manage since you have to look at the actual
component code to see it.




Not really, since you can pull out the custom logic that you have in your HOCs or renderProps in a custom hook and look for its implementation instead of understanding what actually is going on in the actual component.






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',
    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%2f53387613%2fwhen-and-how-to-choose-between-react-hooks-and-old-hoc-props-passing%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








    up vote
    1
    down vote













    Hooks are still in alpha and the devTools support is still in development for it. And according to the React FAQs hooks can be used as an alternative to renderProps and HOCs, but can coexist with them




    Often, render props and higher-order components render only a single
    child. We think Hooks are a simpler way to serve this use case. There
    is still a place for both patterns
    (for example, a virtual scroller
    component might have a renderItem prop, or a visual container
    component might have its own DOM structure). But in most cases, Hooks
    will be sufficient and can help reduce nesting in your tree.




    Hooks allow stateful logic in functional components and would be similar to class components in React.




    Hooks are harder to manage since you have to look at the actual
    component code to see it.




    Not really, since you can pull out the custom logic that you have in your HOCs or renderProps in a custom hook and look for its implementation instead of understanding what actually is going on in the actual component.






    share|improve this answer

























      up vote
      1
      down vote













      Hooks are still in alpha and the devTools support is still in development for it. And according to the React FAQs hooks can be used as an alternative to renderProps and HOCs, but can coexist with them




      Often, render props and higher-order components render only a single
      child. We think Hooks are a simpler way to serve this use case. There
      is still a place for both patterns
      (for example, a virtual scroller
      component might have a renderItem prop, or a visual container
      component might have its own DOM structure). But in most cases, Hooks
      will be sufficient and can help reduce nesting in your tree.




      Hooks allow stateful logic in functional components and would be similar to class components in React.




      Hooks are harder to manage since you have to look at the actual
      component code to see it.




      Not really, since you can pull out the custom logic that you have in your HOCs or renderProps in a custom hook and look for its implementation instead of understanding what actually is going on in the actual component.






      share|improve this answer























        up vote
        1
        down vote










        up vote
        1
        down vote









        Hooks are still in alpha and the devTools support is still in development for it. And according to the React FAQs hooks can be used as an alternative to renderProps and HOCs, but can coexist with them




        Often, render props and higher-order components render only a single
        child. We think Hooks are a simpler way to serve this use case. There
        is still a place for both patterns
        (for example, a virtual scroller
        component might have a renderItem prop, or a visual container
        component might have its own DOM structure). But in most cases, Hooks
        will be sufficient and can help reduce nesting in your tree.




        Hooks allow stateful logic in functional components and would be similar to class components in React.




        Hooks are harder to manage since you have to look at the actual
        component code to see it.




        Not really, since you can pull out the custom logic that you have in your HOCs or renderProps in a custom hook and look for its implementation instead of understanding what actually is going on in the actual component.






        share|improve this answer












        Hooks are still in alpha and the devTools support is still in development for it. And according to the React FAQs hooks can be used as an alternative to renderProps and HOCs, but can coexist with them




        Often, render props and higher-order components render only a single
        child. We think Hooks are a simpler way to serve this use case. There
        is still a place for both patterns
        (for example, a virtual scroller
        component might have a renderItem prop, or a visual container
        component might have its own DOM structure). But in most cases, Hooks
        will be sufficient and can help reduce nesting in your tree.




        Hooks allow stateful logic in functional components and would be similar to class components in React.




        Hooks are harder to manage since you have to look at the actual
        component code to see it.




        Not really, since you can pull out the custom logic that you have in your HOCs or renderProps in a custom hook and look for its implementation instead of understanding what actually is going on in the actual component.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 at 6:54









        Shubham Khatri

        76.2k1388126




        76.2k1388126






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53387613%2fwhen-and-how-to-choose-between-react-hooks-and-old-hoc-props-passing%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







            Popular posts from this blog

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            Refactoring coordinates for Minecraft Pi buildings written in Python