React docs on "Building Your Own Hooks"

Please provide guidance if returning elements (or ()=>elements) from custom hook is a good practice or not.

We have a PageLayout component like the following in our own app:

    <PageLayout
      topBarButtons={..}
      onRender={..}
    />

We want to encapsulate topBarButtons and onRender logic within a custom hook, so that the hook is reusable and shippable without PageLayout. (topBarButtons and onRender will share some state, and useOurHook returns [topBarButtons, onRenderFunc]).

This works fine, if not perfect, for me. But since there are so few custom hook example that returns UI elements (or function that returns UI elements like onRender), the team have doubt about this pattern.

I know the doc has the following statement, but I think this is a very common scenario that deserves a sentence or two in the React docs.

"useYourImagination()
Custom Hooks offer the flexibility of sharing logic that wasn’t possible in React components before. You can write custom Hooks that cover a wide range of use cases like form handling, animation, declarative subscriptions, timers, and probably many more we haven’t considered."

Commencez par la page de documentation "Building Your Own Hooks" et examinez les recommandations et les exemples existants concernant les Hooks personnalisés. Ajoutez une explication concise indiquant si le fait de retourner des éléments ou des fonctions qui retournent des éléments constitue un modèle approprié, y compris le scénario d’état partagé décrit ici ; la page doit répondre à la question de l’équipe sans nécessiter le contexte propre à l’application de cette issue.