This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
@dnolen: added a diff to the wiki containing
ui docs: https://github.com/omcljs/om/wiki/Documentation-(om.next)/_compare/49eee8c3717b41a2a6980cc9a57cfc8b77d30402...0890322afd107d69d6ada94ccc3ee198b40af6ec
also added a simple explanation to the FAQ regarding component local state in
componentWillUpdate. diff here: https://github.com/omcljs/om/wiki/Om-Next-FAQ/_compare/64f4e37e337b11efe9c9f07393782df55c7cd5de...e64bbf03a18e54e632571990239d77251f0117f7
is there something specific you have to do when running any of the builds in om? I get errors on the deps.cljs file for not containing an ns form….looks like it’s just there to point to the externs so guessing i can remove it and add externs to whatever build i need but is there some other way I should be running those builds?
I guess it is not documented anywhere how to build Om/Next?? There's this question http://stackoverflow.com/questions/34477057/including-om-next-source
yeah would be nice to add documentation to the readme about running the tests and such
How are people writing their
main functions for launching CLJS/OM “apps” - for instance I have at least 3 different “root” applications - is just conditionally “launching” them based on dom nodes the current practice? ala https://gist.github.com/drusellers/27cbd0c22217930fde27