commit
f7bd09f1be
4 changed files with 5 additions and 5 deletions
|
@ -2751,7 +2751,7 @@ I wonder?</p>
|
|||
(group-lines))]
|
||||
{:ns ns
|
||||
:groups groups}))
|
||||
</pre></td></tr><tr><td class="docs"><h2>Ouput Generation</h2>
|
||||
</pre></td></tr><tr><td class="docs"><h2>Output Generation</h2>
|
||||
</td><td class="codes"><pre class="brush: clojure"></pre></td></tr><tr><td class="docs"><p>Generates an uberdoc html file from 3 pieces of information:</p>
|
||||
|
||||
<ol>
|
||||
|
@ -3199,7 +3199,7 @@ saying that all this is WIP and will prabably change in the future.</p>
|
|||
"SyntaxHighlighter.defaults['gutter'] = false;
|
||||
SyntaxHighlighter.all()"]]]))
|
||||
</pre></td></tr><tr><td class="docs"><p>Syntax highlighting is done a bit differently than docco. Instead of embedding
|
||||
the higlighting metadata on the parse / html gen phase, we use <a href="http://alexgorbatchev.com/SyntaxHighlighter/">SyntaxHighlighter</a>
|
||||
the highlighting metadata on the parse / html gen phase, we use <a href="http://alexgorbatchev.com/SyntaxHighlighter/">SyntaxHighlighter</a>
|
||||
to do it in javascript.</p>
|
||||
</td><td class="codes"><pre class="brush: clojure"></pre></td></tr><tr><td class="docs"><p>This generates a stand alone html file (think <code>lein uberjar</code>).
|
||||
It's probably the only var consumers will use.</p>
|
||||
|
|
|
@ -386,7 +386,7 @@
|
|||
|
||||
|
||||
;; Syntax highlighting is done a bit differently than docco. Instead of embedding
|
||||
;; the higlighting metadata on the parse / html gen phase, we use [SyntaxHighlighter](http://alexgorbatchev.com/SyntaxHighlighter/)
|
||||
;; the highlighting metadata on the parse / html gen phase, we use [SyntaxHighlighter](http://alexgorbatchev.com/SyntaxHighlighter/)
|
||||
;; to do it in javascript.
|
||||
|
||||
(defn uberdoc-html
|
||||
|
|
|
@ -105,7 +105,7 @@
|
|||
"GENERATED ALWAYS AS IDENTITY")
|
||||
|
||||
(defn strict-eval-op-fn
|
||||
"`strict-eval-op-fn` is used to define functions of the above pattern for fuctions such as `+`, `*`, etc. Cljs special forms defined this way are applyable, such as `(apply + [1 2 3])`.
|
||||
"`strict-eval-op-fn` is used to define functions of the above pattern for functions such as `+`, `*`, etc. Cljs special forms defined this way are applyable, such as `(apply + [1 2 3])`.
|
||||
|
||||
Resulting expressions are wrapped in an anonymous function and, down the line, `call`ed, like so:
|
||||
|
||||
|
|
|
@ -27,7 +27,7 @@
|
|||
Provides the following variables to the assertion context:
|
||||
|
||||
* `number-of-generated-pages` - result of running the `doc-generator`
|
||||
function (which should ultimately call one of the marginalias' own
|
||||
function (which should ultimately call one of the Marginalia's own
|
||||
functions.
|
||||
|
||||
* `project-name` - the name of the project
|
||||
|
|
Loading…
Reference in a new issue