This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-10
Channels
- # announcements (1)
- # asami (44)
- # babashka (62)
- # beginners (84)
- # calva (42)
- # cider (5)
- # clj-kondo (32)
- # cljs-dev (8)
- # clojure (61)
- # clojure-australia (3)
- # clojure-berlin (1)
- # clojure-europe (12)
- # clojure-japan (3)
- # clojure-nl (4)
- # clojure-serbia (5)
- # clojure-spec (1)
- # clojure-uk (9)
- # clojurescript (31)
- # community-development (21)
- # conjure (5)
- # cursive (17)
- # datomic (14)
- # emacs (10)
- # etaoin (1)
- # figwheel-main (1)
- # fulcro (9)
- # garden (5)
- # graalvm (16)
- # helix (7)
- # honeysql (13)
- # jackdaw (25)
- # jobs (2)
- # lsp (21)
- # malli (25)
- # missionary (2)
- # mount (3)
- # off-topic (12)
- # practicalli (3)
- # re-frame (43)
- # reagent (45)
- # reitit (36)
- # releases (6)
- # remote-jobs (2)
- # reveal (28)
- # rewrite-clj (7)
- # shadow-cljs (45)
- # slack-help (4)
- # spacemacs (5)
- # sql (23)
- # startup-in-a-month (7)
- # tools-deps (59)
- # vim (26)
getting a weird error with the fulcro.nteworking.file-upload tooling of Exception while converting mutation with file uploads. Error: Cannot write Function. can’t seem to figure out what might be causing that, and pretty sure I’m using the api correctly. any. pointers on where to look?
as far as I can tell, the root of the issue seems to be my remote calling using m/returning. commenting that out and just setting the remote declaration to be true works as expected
Yeah, it’s funny how this works. That code has been stable and untouched (but broken with returning ) for over a year. Just this week 2 different people have run into it. I’ve had other parts of the system that were the same way. Were busted basically forever, and then all of a sudden multiple people discover it at the same time.
Fulcro 3.4.19 just released. Includes improved dev-time error messages. This was a combined effort of @holyjak and myself. There are more improvements planned, but wanted to go ahead and get these out. holyjak and @alex-eberts are helping add web links to all of the error messages, and a new appendix in the developers guide that will help you understand the error messages, and will refer to the sections of the book you should read when you get them.
9