0.3.3 doesn't work with with Om 0.8.0 and react 0.12.2
Closed this issue · 13 comments
Tested it, reverted back to 11.1. Om 0.8.0 downloads 0.12.2. My HTML references 0.11.1. Tried to use 0.12.2, but that didn't work. Not sure how long this bastardization combination will continue. I guess at some point I will have to stop upgrading Om or om-bootstrap.
You can make it work but some changes are required. om-bootstrap
explicitly depends on om-0.7.1
, so add this to your project.clj
:
[racehub/om-bootstrap "0.3.3" :exclusions [om]]
[org.om/om "0.8.0"]
Also, in react-0.12.2
isValidComponent
has been renamed to isValidElement
. If you're planning to use advanced optimizations then I suggest adding a local copy of om-bootstrap
to checkouts/
and replacing the two occurrences of isValidComponent
in modal.cljs
and util.cljs
.
Perhaps om-bootstrap
could change the dependency to [om "0.7.3" :scope "provided"]
?
that's a good call. I didn't realize that David would change the org name in his dependency, which kills dependency resolution. I'll make that change today.
Okay, I've just pushed 0.3.4-SNAPSHOT
. Can you guys try and let me know if it works? Here's the change:
Now that Om 0.8.0 is out, once we fix that issue I'm down to start pushing toward 0.4.0 on develop. @lostman, I'd take a pull req fixing those two references and other changes if you want. Thanks!
Okay, releasing 0.3.4 now. Give that a try. Also, I'm finally getting around to upgrading this lib to 0.8.0 today! The clone-with-props bug should get fixed by tomorrow. Thanks for your patience, guys.
Awesome that you are still on to it 👍 Thanks.
Thanks, looking forward to upgrading everything ;-)!
On Thu, Jan 29, 2015 at 12:38 AM, lgrapenthin notifications@github.com
wrote:
Awesome that you are still on to it [image: 👍] Thanks.
—
Reply to this email directly or view it on GitHub
#42 (comment).
Is it now working with om 8? Our production app quickly stops rendering and spams react errors in the console. I am asking because if it is supposed to work, we'd schedule debugging our code against it.
@lgrapenthin, I wasn't able to get to it before a weekend trip - I'm REALLY hoping I can do this today and get the 0.8.0 bugs ironed out. Thanks for hanging with me, guys.
Okay, fixed! 0.4.0-SNAPSHOT should be good to go with 0.8.x.
Great! I am looking forward to testing it!
Thanks for all your hard work!
regards,
Mark
On Sat, Feb 7, 2015 at 10:58 PM, Sam Ritchie notifications@github.com
wrote:
—
Reply to this email directly or view it on GitHub
#42 (comment).