iirc the first argument to defnc provides the display name of a component. it shouldn't have $ symbols in it, I think

I think this was the case a while ago, but now it isn’t. E.g.,

(defnc UnderConstructionRenderer
  [props]
  ($ rn/SafeAreaView {:style {:flex 1 :justifyContent "center" :alignItems "center"}}
     ($ rne/Text {:h2 true} "Under Construction")))

I really hate this check, it's totally unnecessary. Here's what I suggested before but the last person said it didn't work, you could try it though: https://clojurians.slack.com/archives/CRRJBCX7S/p1694105114390509?thread_ts=1694096188.205379&cid=CRRJBCX7S

I would open an issue with react-navigation to remove this warning or allow it to be turned off if I were you

Thank you @U4YGF4NGM. I will do that.

Frustratingly, it looks like react-navigation doesn't check the displayName but rather the name property. This is something that helix doesn't control, it's based on how your build outputs the JS. https://github.com/react-navigation/react-navigation/blob/d90ed7665be74c570ed2a6a4da612230fcf6a01c/packages/core/src/useNavigationBuilder.tsx#L222

There seems to be a way to provide a function returning an element as a child of the Screen. However, it needs to be memoized.

(let [render-my-component (use-callback [my-component] (fn renderMyComponent [props] ($ my-component {& props})))]
   ($ Screen render-my-component))

or something to that effect

I have this:

(defn wrap-nav-screen [Component] (-> Component (h/memo)))

($ Screen {:name "Home" :component (wrap-nav-screen Home)})

Thank you for your suggestion @U4YGF4NGM. My solution was incorrect.