This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-22
Channels
- # babashka (36)
- # beginners (42)
- # calva (6)
- # chlorine-clover (25)
- # cider (31)
- # clara (5)
- # clj-kondo (55)
- # cljdoc (3)
- # cljs-dev (7)
- # cljsrn (3)
- # clojure (73)
- # clojure-brasil (6)
- # clojure-europe (8)
- # clojure-italy (2)
- # clojure-nl (3)
- # clojure-norway (1)
- # clojure-spec (3)
- # clojure-sweden (4)
- # clojure-switzerland (2)
- # clojure-uk (29)
- # clojurescript (93)
- # conjure (21)
- # data-science (14)
- # datomic (19)
- # emacs (4)
- # exercism (3)
- # figwheel-main (38)
- # fulcro (38)
- # graalvm (42)
- # graphql (5)
- # jackdaw (3)
- # jobs (1)
- # joker (2)
- # lambdaisland (1)
- # leiningen (31)
- # malli (8)
- # meander (5)
- # off-topic (27)
- # pathom (2)
- # pedestal (28)
- # re-frame (25)
- # reagent (2)
- # reitit (11)
- # releases (3)
- # remote-jobs (1)
- # rum (1)
- # shadow-cljs (63)
- # spacemacs (17)
- # sql (1)
@tony.kay have sent you a PR for a small bug fix - https://github.com/fulcrologic/fulcro-rad/pull/41
I'm playing with the fulcro-native-template and I'm having trouble keeping a repl connected. I start and run the example app just fine. I can connect to the shadow-cljs repl with calva in vscode. The issue is that as soon as I made any edit expo reloads the whole app which silently breaks the calva repl connection requiring me to disconnect and reconnect it. Sorry if this something obvious, I'm very new to clojure and am not accustomed to the tooling yet.
I've already done that. Shadow hot reloads everything just fine, the problem is that immediately afterward expo behaves like an entirely new bundle was built (shows the downloading js bundle popup) and hard-reloads the app.
There's some strange interaction between vscode/calva and shadow-cljs making expo think it needs to constantly build a new bundle. Likely "because windows". You're right, nothing to do with Fulcro though, thanks for the input š
An version bump to latest Fulcro, fulcro-native, expo, and shadow-cljs has magically resolved this. I haven't learned enough about the tooling yet to figure out exactly why. There's a mountain of new knowledge to tackle coming from TS/react-native to cljs and Fulcro haha. Would it be useful for me a send a PR to bump the dep versions on the fulcro-native-template or is there a reason to keep them as-is?
So probably a simple thing, but I am a bit stuck with it: I have a component with a query and an ident, and in its parent, I have {:ui/child-data (comp/get-query Child)}
in the query. Now calling df/load!
with the [:component/id ::Parent :ui/child-data]
target loads a list of {:child/id uuid}
into ui/child-data, and normalizes the actual data into the database at the :child/id key.
This is fine. But... When I now render the child components using (def ui-child (comp/factory Child {:keyfn :child/id}))
and then (mapv ui-child child-data)
it only has its ident populated with the id. Which makes sense considering child-data only contains the idents.
How do I populate the rest of the child's props now?
Obviously I could "catch" the data in :post-action
of df/load, but that feels very very wrong.
not sure what you mean by āpopulate the res of the child propsāā¦didnāt you load them???
The load call?
(df/load! this :example/all-entries Child {:target [:component/id ::Parent :ui/child-data]})
And it loads fine. :ui/child-data
contains all idents of the entries, and the data itself gets stored at the root point of the client databasethe macro tries to help you catch a number of those kinds of errors, but I guess it still misses some
let me know when youāre to the point of slapping your head and thinking āwhat did I find so hard about this??ā š
I think clj-kondo will soon have support for catching problematic calls to macros: https://www.reddit.com/r/Clojure/comments/hcnfwl/some_preliminary_docs_for_an_upcoming_cljkondo/ maybe in the future we won't even need to run code to see problems there
I made a wrapper to use IBM's Carbon Design System with Fulcro: https://gitea.lyrion.ch/zilti/carbon-wrapper
Awesome! I think I'll use it on my next project actually, since semantic is dead from all appearances.
Yea, unfortunately it seems pretty dead, as the main maintainer moved on to Microsoft... It's a shame, it's really nice to work with. I'm using Semantic for a project at work currently
I'm in a similar position. I didn't know how dead semantic was when I started the company project. Fortunately everything still works -- compatibility is one of the very few things about the web that is nice.
Nice. Btw. https://fomantic-ui.com/ is still maintained and tries to be compatible with semantic-ui, seems to be a drop-in replacement. Especially the build system just works.