Avery

Makes sense, thanks! I'll have a peruse and see if it's on a branch somewhere :)

I remembered seeing the issues about it not working through `stack/cabal` so I too was quite surprised when it 'worked' with `cabal test`. I'm guessing cabal has some virtual terminal,...

Also encountering this. Plus, the boolean fields in the schema are listed as `type: boolean` but they are encoded as strings over the enum `"true", "false"`.

How about having both examples in the same `after`? something like ``` aFixedOneWay = ... aFixedTheOther = ... ```

I think having a "See Also" could be useful in this case. Though, if we can pinpoint exactly when one happens vs the other, that could be worth documenting?

I think this can now be closed?

We do not have *full-text* search.

https://stackoverflow.com/questions/17207458/how-to-add-google-analytics-tracking-id-to-github-pages

A temporary workaround is to use `> -` as bullets. that seems to work.