You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to build complex features like an interactive debugger. Fortunately, the assumption turned out to be correct.
240
240
Today <code>cider-nrepl</code> provides pretty much everything that a Clojure development environment might need (and more).</p>
241
241
</div>
242
-
<divclass="literalblock">
243
-
<divclass="content">
244
-
<pre> We quickly
245
-
realized that there was nothing CIDER specific in those middleware and we've
246
-
started to encourage more tool authors to leverage them. Today `cider-nrepl` is
247
-
developed and released independently from CIDER and is used by most of the
248
-
nREPL-based editors and IDEs out there, which is a great example of team work.
249
-
Eventually `cider-nrepl` served as the inspiration for more similar
250
-
middleware libraries - e.g. `refactor-nrepl`, `iced-nrepl` and `sayid`.</pre>
251
-
</div>
242
+
<divclass="paragraph">
243
+
<p>We quickly realized that there was nothing CIDER specific in those middleware
244
+
and we’ve started to encourage more tool authors to leverage them. Today
245
+
<code>cider-nrepl</code> is developed and released independently from CIDER and is used by
246
+
most of the nREPL-based editors and IDEs out there, which is a great example of
247
+
team work. Eventually <code>cider-nrepl</code> served as the inspiration for more similar
248
+
middleware libraries - e.g. <code>refactor-nrepl</code>, <code>iced-nrepl</code> and <code>sayid</code>.</p>
252
249
</div>
253
250
<divclass="paragraph">
254
-
<p>More recently we’ve been working to extract the core functionality out of <code>cider-nrepl</code>
255
-
into a <ahref="https://github.com/clojure-emacs/orchard">REPL-agnostic library</a>.<supclass="footnote">[<aid="_footnoteref_1" class="footnote" href="#_footnotedef_1" title="View footnote.">1</a>]</sup></p>
251
+
<p>In 2019, the core functionality has been extracted out of <code>cider-nrepl</code> into
252
+
<ahref="https://github.com/clojure-emacs/orchard">Orchard</a>, a REPL-agnostic library.</p>
256
253
</div>
257
254
<divclass="paragraph">
258
255
<p>You can check out <ahref="https://www.youtube.com/watch?v=4X-1fJm25Ww">this talk</a>, which explores the birth of
259
256
<code>cider-nrepl</code>.</p>
260
257
</div>
261
-
<divid="footnotes">
262
-
<hr>
263
-
<divclass="footnote" id="_footnotedef_1">
264
-
<ahref="#_footnoteref_1">1</a>. This process started in 2019.
<p>Toggles the viewing mode of the inspector. This influences the way how inspector is rendering the current value. <code>:normal</code> is the default. When view mode is <code>:object</code>, any value will be rendered as a Java object (fields shown as is). View mode is automatically reset back to normal when navigating to child values.</p>
2059
+
</div>
2060
+
<divclass="dlist">
2061
+
<dl>
2062
+
<dtclass="hdlist1">Required parameters</dt>
2063
+
<dd>
2064
+
<divclass="ulist">
2065
+
<ul>
2066
+
<li>
2067
+
<p><code>:session</code> The current session</p>
2068
+
</li>
2069
+
</ul>
2070
+
</div>
2071
+
</dd>
2072
+
<dtclass="hdlist1">Optional parameters</dt>
2073
+
<dd>
2074
+
<p></p>
2075
+
</dd>
2076
+
<dtclass="hdlist1">Returns</dt>
2077
+
<dd>
2078
+
<divclass="ulist">
2079
+
<ul>
2080
+
<li>
2081
+
<p><code>:doc-block-tags-fragments</code> May be absent. Represent the 'param', 'returns' and 'throws' sections a Java doc comment. It’s a vector of fragments, where fragment is a map with <code>:type</code> ('text' or 'html') and <code>:content</code> plain text or html markup, respectively</p>
2082
+
</li>
2083
+
<li>
2084
+
<p><code>:doc-first-sentence-fragments</code> May be absent. Represents the first sentence of a Java doc comment. It’s a vector of fragments, where fragment is a map with <code>:type</code> ('text' or 'html') and <code>:content</code> plain text or html markup, respectively</p>
2085
+
</li>
2086
+
<li>
2087
+
<p><code>:doc-fragments</code> May be absent. Represents the body of a Java doc comment, including the first sentence and excluding any block tags. It’s a vector of fragments, where fragment is a map with <code>:type</code> ('text' or 'html') and <code>:content</code> plain text or html markup, respectively</p>
2088
+
</li>
2089
+
<li>
2090
+
<p><code>:path</code> Printed representation of current inspector path.</p>
2091
+
</li>
2092
+
<li>
2093
+
<p><code>:status</code> "done"</p>
2094
+
</li>
2095
+
<li>
2096
+
<p><code>:value</code> The inspector result. Contains a specially-formatted string that can be <code>read</code> and then rendered client-side.</p>
<p>[DEPRECATED - <code>use test-var-query</code> instead] Run all tests in the project. If <code>load?</code> is truthy, all project namespaces are loaded; otherwise, only tests in presently loaded namespaces are run. Results are cached for exception retrieval and to enable re-running of failed/erring tests.</p>
2797
+
<p>[DEPRECATED - use <code>test-var-query</code> instead] Run all tests in the project. If <code>load?</code> is truthy, all project namespaces are loaded; otherwise, only tests in presently loaded namespaces are run. Results are cached for exception retrieval and to enable re-running of failed/erring tests.</p>
<p>[DEPRECATED - <code>use test-var-query</code> instead] Run tests in the specified namespace and return results. This accepts a set of <code>tests</code> to be run; if nil, runs all tests. Results are cached for exception retrieval and to enable re-running of failed/erring tests.</p>
3094
+
<p>[DEPRECATED - use <code>test-var-query</code> instead] Run tests in the specified namespace and return results. This accepts a set of <code>tests</code> to be run; if nil, runs all tests. Results are cached for exception retrieval and to enable re-running of failed/erring tests.</p>
0 commit comments