Juho Teperi

Also, there are SOME cases where providing JSDoc type annotations in extern files could result in better Closure compiled code, e.g. `/** @const {boolean} */ var CONSTANT_VALUE = false;` and...

@honzabrecka It should be `[cljsjs.ts/react "16.0.2-0"]`, we don't want to create a new group for each package. Anyway, externs are not really related to global-exports, so we could open separate...

Most of Node modules won't need externs. Only special cases like React will need them. I'd have extern only packages only provide externs, without npm-deps.

I wrote some docs about naming convention and global-exports: https://github.com/cljsjs/packages/wiki/Unified-module-names-and-global-exports Naming convention and global-exports are separate, and either could be implemented without other. But both are needed to be able...

I don't think this is possible with letk/plumbing syntax. You can use `:query` to set the Schema using normal Schema: https://github.com/metosin/compojure-api/blob/master/src/compojure/api/meta.clj#L205. Though this doesn't solve destructuring.

@t-jones Yes we are planning on using metadata set by plumbing letk. But anyway, that won't help in this case, the metadata is purely for documentation, the default value itself...

Here's a sample of using Buddy: https://gist.github.com/Deraen/ef7f65d7ec26f048e2bb

We already have separate example repo (https://github.com/metosin/compojure-api-examples) should we extend that or should we have all examples in this repo? No sense having multiple examples here and single example on...

```clj (s/def :file/filename string?) (s/def :file/content-type string?) (s/def :file/size integer?) (s/def :file/tempfile #(instance? java.io.File %)) (s/def ::file (st/spec {:spec (s/keys :req-un [:file/filename :file/content-type :file/size] :opt-un [:file/tempfile]) :json-schema/type "file"})) ```

Bat-test contains implementation of tools.namespace eftest integration: https://github.com/metosin/bat-test/blob/master/src/metosin/bat_test/impl.clj#L127 The code uses low level c.t.n functions (dir and track namespaces) of so that it can also use the changed file information...