This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
If, in one task, you add and commit some new files as resources, how would you access them by filename in tasks after that in the same pipeline?
boot.core/user-dirs
, input-dirs
, user-files
, etc. return unordered sets, through which one would have to filter through sequentially to find a specific output file at a specific input path.
You can also get TmpFile records like this (get (:tree fileset) “your-file.edn”)
@martinklepsch: would you be interested in hacking on this guy at clojutre https://github.com/adzerk-oss/zerkdown
it's an abstract markdown parser, i.e. you configure it with the tags it will parse and it produces an AST that you can use to generate whatever you want, not just html
some examples of what it can parse now: https://github.com/adzerk-oss/zerkdown/tree/master/test/adzerk/zerkdown/parser_test
also some fancy macros to delay evaluation for recursive parsing https://github.com/adzerk-oss/zerkdown/blob/master/src/adzerk/zerkdown/parser.clj#L48-L60
@micha I don't immediately see what I would do there tbh. :satisfied:
@micha: why would I use that in comparison to some plain wrappers that are elided when goog.DEBUG
is nil
?
(when ^boolean goog.DEBUG
(js/console.log “x”))
:compiler-options {:closure-defines {“goog.DEBUG” false}}
It’s basically the same as the goog-define
stuff we talked about a day ago or so
basically i don't ever want to mess with :compiler-options
because it's closed, not open
Is spy basically like a trace? print thing, return thing?
Probably I missed some aspect but I think in general totally possible:
(defn spy-> [f msg]
(when ^boolean goog.DEBUG (log f))
f)
In theory that when call isn’t even necessary if your log fn already does it of course
but it means messing w/ macros and more code you need to maintain
The above will too.
I don’t think one approach is more valid than the other. I happily take the shortcut the closure compiler provides if it does what I need
and i bet if i wrote it as goog.DEBUG functions i'd end up writing macros to generate the functions
String interpolation is cool
i'm basically factoring things out of the current project at work and putting them in the oss pile
I’d like to show off an alternative impl but I guess that has to wait for now
haha — My feeling is it would be much easier to read but that’s just speculation 😄