This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-30
Channels
- # aws (5)
- # aws-lambda (2)
- # beginners (29)
- # boot (5)
- # cider (3)
- # cljs-dev (3)
- # cljsjs (2)
- # clojure (112)
- # clojure-austin (1)
- # clojure-brasil (2)
- # clojure-italy (9)
- # clojure-nl (2)
- # clojure-russia (5)
- # clojure-spec (49)
- # clojure-uk (41)
- # clojurescript (157)
- # core-logic (5)
- # crypto (1)
- # cursive (12)
- # data-science (38)
- # datomic (31)
- # emacs (3)
- # events (2)
- # garden (3)
- # graphql (10)
- # immutant (4)
- # jobs (3)
- # juxt (5)
- # klipse (1)
- # luminus (3)
- # off-topic (40)
- # om (1)
- # onyx (39)
- # other-languages (7)
- # protorepl (3)
- # re-frame (40)
- # reagent (60)
- # ring (8)
- # ring-swagger (14)
- # shadow-cljs (159)
- # spacemacs (1)
- # specter (6)
- # uncomplicate (3)
- # yada (2)
@mhuebert https://github.com/mhuebert/shadow-re-frame has no link to the demo? didn’t you have a live demo somewhere?
I’m getting very tired of me accidentally printing the CLJS compiler state at the REPL
in my fork of re-frame-trace I started writing some namespace-aware truncation functions, as I needed a way to recursively print abbreviated Clojure forms https://github.com/mhuebert/re-frame-trace/blob/preview-event-params/src/day8/re_frame/trace/pretty_print_condensed.cljs
re: re-frame-panel - yeah that’s weird. i think they are working on alternate ways to view that widget, trying to limit the amount of stuff I put in my re-frame-trace fork
so that code (pretty-print-condensed) is not there yet, but may be in the right direction, as it emits a string (not a React component) and focuses on truncation of individual elements of the structure
eg. “print this whole structure but limit length of any individual element to 30 chars”
the re-frame-trace app db explorer utilizes cljs devtools, but i was there as that was coded and it was really awkward because cljs devtools is tightly coupled to jsonml, this format used by chrome devtools
i plan to continue developing the value-viewer that is used by maria, which you’ve seen earlier
just landed support for css reloading in [email protected]
i’m trying to understand exactly how paths work when requiring stuff from npm. eg someting like “@material/menu/util”, given that menu
is this dir: https://github.com/material-components/material-components-web/tree/master/packages/mdc-menu
there is an index.js
, which exports: export {MDCSimpleMenu, MDCSimpleMenuFoundation, util};
node resolve rules in a nutshell: first check if there is an exact match (with ext), then test with added .js
ext
with ["@material/menu/util" :refer [getTransformPropertyName]]
I am seeing ReferenceError: module$node_modules$$material$menu$util is not defined
I’ll fix that next, it re-appeared when I reworked the JS support recently because of this weird fabric.js
issue
so, this should work:
["@material/menu/simple/foundation" :as MDCSimpleMenuFoundation]
["@material/menu/util" :refer [getTransformPropertyName]]
unfortunately this is not officially supported yet, so beware when adding this to a library
ah. i was wondering about that. I saw the discussion in cljs-dev about this :default stuff.
:default
only works in shadow-cljs, not sure yet whether it will be adopted in CLJS core
I got tired of writing thing/default
very very quickly when testing the ES6 support, thats why I added the :default
note that you do not have to use :default MDCSimpleMenuFoundation
:default thing
also works since you can chose the name
@jiyinyiyong not in release mode, only watch
.
its only watch/reload for now .. there is no support for directly bundling css in any way
it watches the :watch-dir
(or :http-root
) and then replaces <link rel="stylesheet" href="/css/main.css">
tags if /css/main.css
changes
interesting by I will keep using Webpack in my cases... I have to make sure it's correctly bundled.
although I don't have much handwritten CSS in my current workflow https://github.com/mvc-works/coworkflow/blob/master/entry/main.css
@jiyinyiyong @mhuebert you both seem to use cljs-devtools
. how come? is the console support shadow-cljs
adds not enough?
@thheller I don’t actually use it, only included it in that example because of re-frame-trace
anyways bundling CSS is really huge work, there are style-loader
css-loader
file-loader
url-loader
involved just to bundle CSS with fonts...
actually most of my CSS lives in ClojureScript https://github.com/Cirru/cumulo-editor/blob/master/app/src/app/comp/leaf.cljs#L35 since I don't care about compatibility in my personal stuffs.. I would like to drop Webpack... just I still need to bundle CSS correcly.
(replicate via npm install firebaseui
and then include sth like ["firebaseui" :as firebase-ui]
in a namespace)
requiring "firebase/app.js"
appears to work, but not "firebase/app"
, and since firebaseui is the one doing the require, i can’t change that
I do ignore those currently because I don’t want to run into situations where 2 versions of one package are loaded
interesting:
--- externs.shadow.js:3225
Parse error. Character '$' (U+FF04) is not a valid identifier start char
and last line of that file is ShadowJS.prototype.$;
funny that I’m using a isJSIdentifier
method from Closure that is supposed to check this 🙂