Fork me on GitHub
#om
<
2017-10-11
>
eugekev01:10:03

Any fulcro and fulcro-css users out there in Om Next land? Having trouble writing the local-rules css for nested selectors, e.g. “.main-nav li a:hover {… }”

sundarj01:10:12

ask in #fulcro 🙂

wilkerlucio02:10:20

@eugekev also, check Garden documentation, fulcro-css generates de styles using that

eugekev02:10:24

Ah, thanks @U61HA86AG Hadn’t seen the different channel

timovanderkamp05:10:20

[:.main-nav [:li [:a [:&:hover {}]]]] is a nested css rule to target the “a” tags within your main-nav’s list items

timovanderkamp05:10:20

[:.main-nav [:li [:a [:&:hover {}]]]] is a nested css rule to target the “a” tags within your main-nav’s list items

eugekev10:10:49

Thanks @timovanderkamp - that does indeed work. As an aside, and having worked with straight React/ES6 to better understand it first, I agree its nice to embed markup with the component. I have to say though that this nested garden syntax for CSS is a certainly bit more complex to grok than separate entries in a normal CSS file. Will have to see how easy this gets as I get better at it.

eugekev10:10:27

Would love to hear what people feel is the best routing for Om Next. Are people mostly using Compassus? Or rolling their own ala https://anmonteiro.com/2016/02/routing-in-om-next-a-catalog-of-approaches/

wilkerlucio17:10:36

for what I've seem, most people are rolling their own. since you are using Fulcro I recommend you check the approach suggested there, since it's one already tested with this stack

nha16:10:52

@eugekev I think fulcro provides routing

eugekev19:10:43

Thanks @nha - had missed that but see it now in the docs.