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."

"Building Your Own Hooks" のドキュメントページから始め、custom Hooks に関する既存のガイダンスと例を確認してください。要素、または要素を返す関数を返すことが適切なパターンかどうかについて、このページで説明されている共有状態のシナリオも含め、簡潔な説明を追加してください。このページだけでチームの質問に答えられるようにし、この issue のアプリケーション固有のコンテキストを必要としないものにしてください。