This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # alda (1)
- # bangalore-clj (5)
- # beginners (17)
- # boot (392)
- # capetown (4)
- # cider (16)
- # cljs-dev (24)
- # cljsrn (33)
- # clojure (106)
- # clojure-berlin (1)
- # clojure-nl (1)
- # clojure-russia (168)
- # clojure-spec (85)
- # clojure-uk (137)
- # clojurescript (83)
- # clojutre (4)
- # component (10)
- # cursive (6)
- # datavis (9)
- # datomic (11)
- # defnpodcast (15)
- # dirac (4)
- # docker (1)
- # ethereum (1)
- # hoplon (27)
- # jobs (5)
- # jobs-rus (1)
- # lein-figwheel (2)
- # luminus (5)
- # off-topic (5)
- # om (13)
- # onyx (60)
- # parinfer (2)
- # planck (12)
- # proton (2)
- # re-frame (45)
- # rethinkdb (5)
- # ring-swagger (9)
- # spacemacs (9)
- # specter (49)
- # test-check (1)
- # untangled (104)
- # yada (10)
in my app state, I always see a
nil nil key-value pair. Is this normal? Or does it refer to the root object? Or do I have something dangling somewhere? I'm not seeing any warnings in the console, and things appear to be working. Just wondering what that is.
Hi all. Back from vacation. I'll be looking at PRs this morning in more detail. Going to do some testing of my own.
@erichmond I think it is coming along quite well. Om seems to get bug fixes as we push the boundaries (often thanks to @anmonteiro ). We're quite happy with it, and there are now a few things out in the commercial space using it.
nil nil thing is probably an Untangled bug. I've seen it. Have not bothered tracing it down, since it doesn't hurt anything
@jasonjckn I'll give some serious brain cell activity to your PR. I just need to put my brain in gear enough to grok your comments/code.
@tony.kay thanks for responding. what’s your suggestion on if people should adopt it yet? we’re in a position where we need to crank out an MVP and at this point if things aren’t baked well, we’re going ot have to abandon it for time considerations
@erichmond We've got a product in Beta, and I know of at least one other company that does as well. Reframe is a different animal, aimed only at the UI. Om/Untangled are full-stack stories.
I have not tried using Re-frame for anything, so I cannot speak to the relative difficulties in coming up to speed.
@tony.kay thanks! so if I worked with it today, I could get a simple project working end-to-end?
@erichmond If you clone Untangled TODOMvc, you'll have a full-stack working solution in about 5 mins
I'm at one of those other companies with a beta product on Untangled - I think it worked out pretty well for us. Overall my only complaints have been learning curve, and @tony.kay has done a pretty great job building up documentation and tutorials
We started with a prototype (week long spike) on a om.next stack that didn't use untangled - we heard about it after we were done with the prototype and realized it solved almost all of the pain points we were fighting during that first week
part of the beauty of the solution (mostly Om) is the unified approach. The full-stack story is very nice IMHO
I'm not going to say it's a magic bullet - it's still pretty bleeding edge, but we've been pretty happy with it overall.
@erichmond Definitely go through the tutorial, and the getting started videos available from the Untangled website. They'll save you a lot of time, I think.
@erichmond: from the perspective of a re-frame user, you should be able to get the UI up and running very quickly, and the concepts involved are quite simple and straightforward. The tradeoff is that it really only deas with the UI, and doesn't deal with many of the concerns that Om and untangled are aimed at (nothing graphql-like, nothing for normalizing data, etc). If you are looking for a ui for a more traditional rest based app that is targeting primarily one platform, re-frame is an amazing solution. If the really innovative things in om and untangled are what you need, then re-frame is probably not what you are looking for.
@tony.kay so for my PR, the blockers are (1) you want the items-to-defer as a pure function, is that all?
I'd like tests that show it does the right thing in the cases I described (e.g. it currently uses
data-ident, which isn't correct)
@tony.kay i'm still pretty fresh to the code base, I can definitely write more tests and make it pure, but that data-ident part that one function passed to distinct-by I need your help
@tony.kay i don't think skype or hangouts does virtual desktop (?) i know screenhero does
In untangled, are all mutations sent to the server, even if remote isn't set to true? I'm seeing them show up in the logs.
yeah, I'm glad they're coming in handy. I fear the day that IntelliJ changes enough to require me to redo them 😕
I'm still an Emacs user 🙂 Also using Pedestal on the backend instead of untangled server, but they're decoupled enough that it hasn't been an issue.
yeah, we have emacs and vim users here, so the project file is set up to work well for any
I've got a demo tomorrow so I'm finishing up what I need to to make that happen. After that I'm working on lazy loading tabs. Not sure how to scope the queries for the tab based on a setting. For example, say the main tab has a list of cars, and when I select one of the cars, the other tab opens up with details of that particular car.
That's what I was thinking. Have to figure out how to get the app state like I need to. Still need more practice doing that.
1. put the "selected car" in the right object that renders the car 2. put the "which tab is open" value for showing the tab
sometimes a singleton...if it is a single UI element. Tabs are often a single data item that use an ident to switch queries/ui rendering
Right. I was thinking of the singleton for the selected car, independent of the tab. Then the query for the tab would have a link to that singleton
mmm. more likely the object that represents the view of the car (which might be a singleton) would be updated for a field to point at the right car (which would end up with recursive queries, etc)
I'm also interested in the full-stack testing stuff that the Ladderlife people have with Cellophane.
but it does exercise both the client and server...just in a CI compatible, non-breaking way
well, that's good to hear 🙂 Maybe this weekend I'll take a look. My backend is pretty well covered. Front-end needs more automated testing.
it doesn't test the "rendering" of the UI, but it gets at what you really want: making sure the model interactions are correct all the way through