This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-09
Channels
- # aws (3)
- # beginners (61)
- # boot (1)
- # cider (80)
- # clara (5)
- # cljs-dev (5)
- # cljsrn (19)
- # clojure (40)
- # clojure-dev (29)
- # clojure-dusseldorf (2)
- # clojure-greece (21)
- # clojure-italy (16)
- # clojure-russia (7)
- # clojure-spec (31)
- # clojure-uk (70)
- # clojurescript (31)
- # cursive (21)
- # data-science (5)
- # emacs (7)
- # fulcro (23)
- # graphql (4)
- # java (18)
- # jobs (1)
- # jobs-discuss (25)
- # juxt (14)
- # nrepl (2)
- # off-topic (18)
- # om-next (2)
- # onyx (3)
- # re-frame (16)
- # reagent (50)
- # ring-swagger (5)
- # shadow-cljs (70)
- # specter (5)
- # sql (24)
- # tools-deps (16)
- # vim (41)
It's pleasing to see how few changes re-natal has to make to the files generated by react-native init
https://gist.github.com/olivergeorge/d233fede8b3262e05c16b06ae5158861
I’m using ReactNavigation via cljs-react-navigation
and when I try to use setParams
to change e.g. the title of a screen, I’m getting “One of the sources for assign has an enumerable key on the prototype chain. Are you trying to assign a prototype property? We don’t allow it, as this is an edge case that we do not support. This error is a performance optimization and not spec compliant.”
Anyone else seen and/or fixed this?
I think I saw this once when I tried running a side effect that modified the component while it was in the rendering process. You might want to check if you are calling setParams while rendering
Cool, thanks for the pointer
@mfikes I made good and actually put those documents somewhere public:
For anyone curious, this is a series of documents written to help get our team of Clojurescript developers up to speed with developing a React Native app. This is not a survey of all possible approaches, instead it's based on a series of design decisions with associated tradeoffs. You must be this tall to play along: * You're familiar with Clojurescript * You're familiar with re-frame Goals of these documents are a zero-feature release. That is to say app has all necessary building blocks to start adding custom features and the processes for developing, testing and releasing are established:
They need lots of feedback.
Following along should look a lot like this: https://bitbucket.org/olivergeorge/iteration-zero/commits/all
@olivergeorge this is pure gold! I'm not a RN developer but I want to add support for RN to shadow-cljs. Seeing what the issues are with current tooling is tremendously helpful!
yeah, it was insightful jus to try and write them down so the next person wouldn't get tripped up.
I was just reading your write up @olivergeorge, thank you!
I'm no expert though, perhaps playing along will help highlight things for you.
thats exactly the point though. experts know how to navigate around certain things unconsciously and might not even mention those. so every little thing helps.
Has anyone tried replacing the re-natal use-figwheel
command functionality with an equivalent in clojure as part of their figwheel build scripts?
I think it would address: Forgetting to regenerate index.*.js <https://confluence.condense.com.au/display/IZ/Gotcha+%231%3A+Forgetting+to+regenerate+index.*.js> Figwheel eating your index.*.js files <https://confluence.condense.com.au/display/IZ/Gotcha+%234%3A+Figwheel+ate+your+index.*.js>
Perhaps I'm missing good reasons why that's a bad idea.