Clojurians
#om
<
2016-04-07
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

mping08:04:37

is there any boilerplate for om-next with routing , compojure and db access?

anmonteiro12:04:13

@mping: nothing like that, but you can probably start from this: https://github.com/swannodette/om-next-demo/

anmonteiro12:04:41

it doesn't use compojure, but it wouldn't be too hard to use it instead

mping13:04:19

@anmonteiro: and what about routing, any suggestion? I'm quite new to om

anmonteiro14:04:30

@mping: I've written about routing in a blog post, hope you find it useful: http://anmonteiro.com/2016/02/routing-in-om-next-a-catalog-of-approaches/

mping14:04:01

thanks, I'll take a look. I've stumbled upon it before, but I'll read more carefully

curtosis14:04:35

this is exactly the question I was going to start off my morning with. thanks! :simple_smile:

kendall.buchanan20:04:13

Another noob question: What are the most common uses of data normalization in om.next? The tutorial uses a remote service returning two lists with duplicate records. Are there more common use cases?

kendall.buchanan20:04:17

Bit more detailed example.

mahinshaw20:04:12

@kendall.buchanan: Normalization is used to remove redundant data. It relates to normalization in a relational database. I don’t know of any reason’s why you wouldn’t want to normalize your data.

kendall.buchanan20:04:14

I think I got it now – looks like the standard use case is to take a bunch of tables and combine them into more deeply nested graphs.