This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-26
Channels
- # adventofcode (2)
- # beginners (69)
- # boot (37)
- # cider (6)
- # clara (31)
- # cljs-dev (75)
- # cljsrn (5)
- # clojure (72)
- # clojure-dev (7)
- # clojure-italy (11)
- # clojure-nl (8)
- # clojure-russia (2)
- # clojure-spec (56)
- # clojure-uk (54)
- # clojure-za (1)
- # clojurescript (156)
- # cursive (2)
- # datomic (34)
- # emacs (1)
- # fulcro (227)
- # hoplon (74)
- # jobs (1)
- # jobs-discuss (16)
- # leiningen (5)
- # lumo (17)
- # off-topic (9)
- # om (3)
- # onyx (10)
- # other-languages (1)
- # portkey (2)
- # re-frame (2)
- # reagent (36)
- # reitit (1)
- # remote-jobs (1)
- # ring-swagger (8)
- # shadow-cljs (85)
- # slack-help (2)
- # spacemacs (6)
- # specter (3)
- # sql (17)
- # test-check (15)
- # tools-deps (80)
Hi all: does anyone have an approach that works and they like for dealing with CSS and semantic-ui-react
? I've tried a couple of approaches that integrate and compile the semantic-ui less source, but the less4j
compiler (via less4clj
, via boot-less
) produces incorrect css and does not look like it will be fixed any time soon. Is there some other approach that folks have tried? Not really feeling optimistic about just overriding vanilla css.
Does anyone know how to use this library? https://github.com/cljsjs/packages/tree/master/react-datepicker
I think I will be good-to-go if I knew how to place the datepicker component on a page.
I've tried [:> date-picker]
, [date-picker]
, and [:> js/DatePicker]
@zalky i use sass instead of less, but i basically just use unix style tools to watch the css and put it in the right place. i’m using shadow, so that’s easier, because i just launch everything using npm. i actually prefer this because you don’t have to keep cramming stuff into a build tool like lein. i personally am super happy to use standard tools rather than a big opaque monolith
@doubleagent I'd start by figuring out where DatePicker is available on the page. In the chrome devtools, see if window.DatePicker gives you anything
if the readme is correct, [:> js/DatePicker]
should work. What error do you see?
Yeah, i had to do something like (.-default js/Component)
to get it work in the past for default components
@doubleagent, try [:> (.-default js/DatePicker)]
try console.log(window.DatePicker)
see what it returns. You'll see if it has a default export
Thanks @zalky, that worked!
some libs do, others don't
would be a good PR for the cljsjs readme
@pesterhazy a substantial number of those libs need a basic usage example. 😄
true, true
i'm not sure how to do that in my project.
with semantic ui i just linked to the cdn
yeah...
but the css on github looks like sass
you can link to the cdn too: https://cdnjs.com/libraries/react-datepicker
dude, that's awesome
thanks
@lee.justin.m you need a btc tipjar or something
@lee.justin.m, thanks for the response! I use boot so I do have some flexibility in how I pull in stuff. I'd also prefer sass, and looked around to find if there was a sass version, found this (https://github.com/doabit/semantic-ui-sass). Are you using something similar?
@doubleagent no tips needed! i’ve relied on a ton of patient help from people here
@zalky i’m not using semantic myself, but i think the issue of how to deal with compiled css is the same
in a webpack tool chain there was a more obvious way of how to do it. lein, in my opinion, does too many things and does them poorly, and i’ve realized that there’s no benefit to cramming everything into there. much nicer to just write some simple build scripts and use the standard tools. i just have a node-sass -w src/sass/site.scss -o public/css
in my start scripts