This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-27
Channels
- # bangalore-clj (2)
- # beginners (41)
- # cider (14)
- # cljs-dev (12)
- # cljsrn (2)
- # clojure (106)
- # clojure-austin (6)
- # clojure-dev (22)
- # clojure-dusseldorf (1)
- # clojure-france (1)
- # clojure-greece (17)
- # clojure-italy (6)
- # clojure-poland (3)
- # clojure-russia (10)
- # clojure-serbia (5)
- # clojure-spec (24)
- # clojure-uk (100)
- # clojurescript (126)
- # cursive (3)
- # data-science (5)
- # datascript (15)
- # datomic (3)
- # defnpodcast (2)
- # dirac (6)
- # emacs (10)
- # fulcro (121)
- # graphql (30)
- # hoplon (7)
- # jobs (2)
- # leiningen (20)
- # off-topic (14)
- # onyx (3)
- # other-languages (13)
- # pedestal (1)
- # perun (2)
- # planck (41)
- # re-frame (16)
- # reagent (6)
- # reitit (5)
- # remote-jobs (3)
- # ring (1)
- # ring-swagger (17)
- # shadow-cljs (137)
- # spacemacs (6)
- # sql (4)
- # uncomplicate (7)
- # unrepl (56)
- # vim (27)
Hi all, is there any plan to support allowing a user to pass a custom output-wrapper
? https://github.com/clojure/clojurescript/blob/e83cf518ef4d3d6aa9a1cca18dc889efb0eae57f/src/clj/cljs/closure.clj#L862
I’m getting some errors during advanced optimization which would be best addressed by passing in a custom string,
'(function(){\n%output%\n}).call(window)'
to allow the closure to have access to some other context. In this case, I wish to use window
to get access to the global scope.@levitanong :output-wrapper
could easily support function values, feel free to submit a minor enhancement patch
@dnolen on it. Looks like there isn’t a pre-existing ticket for this, given a search for “output-wrapper”.
@dnolen attached the patch. https://dev.clojure.org/jira/browse/CLJS-2423 I was given the option to set the patch to either code or code + test, but I opted not to choose any because I thought I would be able to change later when I actually had a patch to show for it. I don’t know how to change it. 😅
my pleasure!