anyone currently working on an om.next template with figwheel configuration, routing, and other webapp basics already defined with placeholder code to get started? I guess I could try to add om to the luminous template so you can create a new luminous app with +om

@gary: there’s aemette, but I haven’t touched it in a while

https://github.com/anmonteiro/aemette

and also probably not the way I would do routing today

@anmonteiro: i was just about to say, your template doesn't use your own routing library

@gary: aemette was something I put together in December

and I’ve only built Compassus in the beginning of June 🙂

I’ve been meaning to put together a template for a Compassus app, but I’ve been too busy lately

Yeah, I've just started using Compassus. Being new to om and having an enterprise java background, it's all so new and bewildering

One thing I haven't seen anyone address is security and protected routes in SPAs

@gary: While I don;t have that much Om experience I have quite a lot of SPA experience, though more in hybrid apps than in browser apps.

The thing is that access to sensitive data can;t be controlled by the client.

So it's a seperate concern from routes.

Exactly how you handle auth is specific to how you do auth, of course, but....

Of course your flow should keep unauthenticated users from getting to places that require auth, but... that's user experience, not security.

well I'm working one of the best kinds of webapps ever invented, an ecommerce app https://github.com/gdeer81/om-commerce

a robust ecommerce app cuts across a lot of different concerns so writing an om app will force me to deal with a lot of problems versus just donig dev card examples or a todo mvc app

@gary Thats a good approach, I also prefer to test out libs/frameworks with larger scale projects that go beyond todoMVC and “counter” apps. I have attempted building the same application in meteor.js (in its early days), angular, react/flux/redux, om (old), reagent, reframe and now om.next. With each, once you get past the simplicity of a todoMVC demo both in terms of screens and data schema, you start to the see the cracks and steep architecture hill you need to climb before you can even start to focus on the actual business problem. I am still on my quest to find the most productive and clean approach to building larger SPAs but I think CLJS followed by om.next have the most promising foundation to getting me there.

@afhammad: yeah I agree

ki9090909090909090909090909090909090909090909090909090909090909090909090909090bnbnbnbnbnbnbnbnbnbnbnbnbnbnbnbnbnbn

your cat walked on your keyboard

\\\\\\\\\\\\\\\\\\\\\\\\\\\];[p'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''-00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

'

'

'

'

'

'

'

'

@cmcfarlen: whenever you get a chance, try compassus master to see if it fixes your issue with re-reading keys

hopefully fixed in https://github.com/anmonteiro/compassus/commit/1883298c4fd8db2eafe1dcc7c92013bf5d17f8be