The callable constructor proposal was withdrawn because "the same problems can be solved with decorators" but the readme here doesn't show examples of that. Can you please update that for reference? It would be really helpful.

When making a new "mark as note" the text is duplicated and the resulting note controls/handles move to the top left of the artboard, but the note is visually in another place. after spec export however the note shows up where it was visually.

side note: ive also had to ungroup "note-box" that it creates for spec export to even work with notes
![screen shot 2019-02-07 at 12 25 41 pm](https://u

Detailed Description

Update os_env documentation to state where variables should be set for controls using the os_env resource.

Context

Why is thi

Repro:

(deftest a-test
  (st/instrument)
  (binding [s/*explain-out* expound/printer]
    (s/explain-str :foobar/name "")
    ))

lein test

s/*explain-out* should control the success message, not the outer functions

https://github.com/clojure/spec.alpha/blob/5a4834eeb2967b2eca382efe0afcb3f590bdb3c2/src/main/clojure/clojure/spec/alpha.clj#L257

Workaround is

Please add descriptions to functions in the source code, to make it easy to read and understand.

Example:

/**
 *   Transforms an input element....
 * @param {Function} successFn callback function in case of valid input
 * @param {Function} failFn callback function in case of invalid input
 * @param {Array} input
 * @returns {*}
 */
const transform = (successFn: Function, failFn

Hi, @gnl — 

Keep up all the amazing work. Just ran into the strange problem... Here's a function without ghostwheel...

(defn should-return-nil
  [x]
  nil)
=> #'x.asin/should-return-nil
(should-return-nil "")
=> nil
(should-return-nil "")
=> nil

And here's the same function with ghostwheel — it returns seemingly random numbers. I'm wondering if I'm doing somethin

See firsttimersonly.com.

This could serve as a good forcing function towards improving our contribution guidelines, documentation, and making our community more welcoming to newbies.

The docs for "or" look like this:

or (name, ...specs) <-- Looks like you can pass in a bunch of specs like and()

Data must conform to at least one provided spec. The order in which they are validated is not defined. conform returns matched branches along with input data.

const big_or_even = spec.or("big or even", {
  'even': spec.even,
  'big': nr => nr > 1000
})```

Perhaps o

https://github.com/public-transport/friendly-public-transport-format/blob/master/README.md describes the vision, without any examples of the format itself

it links to https://github.com/public-transport/friendly-public-transport-format/blob/master/spec/readme.md that has no introduction or basic examples. It immediately starts from "In order to be able to use this format in both static data and