This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # 100-days-of-code (1)
- # announcements (7)
- # beginners (63)
- # cljs-dev (39)
- # clojure (78)
- # clojure-dev (40)
- # clojure-italy (4)
- # clojure-nl (22)
- # clojure-russia (5)
- # clojure-spec (5)
- # clojurescript (60)
- # cursive (8)
- # datomic (6)
- # emacs (1)
- # figwheel-main (53)
- # fulcro (19)
- # jobs-discuss (11)
- # mount (1)
- # off-topic (3)
- # om (1)
- # pedestal (9)
- # philosophy (1)
- # re-frame (19)
- # reagent (4)
- # reitit (5)
- # shadow-cljs (66)
- # tools-deps (64)
I’ve just released 2.6.1. It includes a new option related to server-side rendering, and better error messages (without the big stack traces!) from
defsc and other macros.
Because in our fulcro app we have big requests we've decided to move some of the querying to a web worker. However I can not seem to hit the entity endpoint from the worker. I'm using html5
fetch with method post, and have made sure the body is the exact same transit object as when sending it from the main app load. But somehow the server sends back a 200 empty response
["^ "]. Any idea what could be happening here?
you’ve looked at the request headers to make sure they are the correct transit type?
I did look at the headers and they were mostly the same, one that was different is that the WW had "Referrer" set. But I can't remember the transit type header.
Okay, I fell back to adding a regular ring handler in
:extra-handlers, but I will inspect the headers again later.
It’s pretty simple to roll your own server, too…easy server is just meant for getting started quickly.
There’s even a
mount example in the book now: http://book.fulcrologic.com/#_rolling_your_own_server
I personally roll my own in new projects, and will probably update the docs at some point and discourage using anything else for projects headed to production.
On my own starcraft project I did roll my own. Using the easy server now because I didn't already have a server before I added fulcro and it's easy 😅
(meaning that the component for the
/ route is shown before transitioning to the route I’m hitting)
Does this bidi setup mean it will first load
(branch "/" (leaf "" :integrations-index) (leaf "index.html" :integrations-index) (branch "integrations/" (param :id) (leaf "" :integration-details))))
:integrations-indexand then the
integrations/branch if going to a