<!-- 
RSS generated by JIRA (4.4#649-r158309) at Wed Jun 19 18:48:12 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://dev.clojure.org/jira/si/jira.issueviews:issue-xml/NREPL-29/NREPL-29.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Clojure JIRA</title>
    <link>http://dev.clojure.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>4.4</version>
        <build-number>649</build-number>
        <build-date>25-07-2011</build-date>
    </build-info>

<item>
            <title>[NREPL-29] Provide a mechanism for overriding an operation</title>
                <link>http://dev.clojure.org/jira/browse/NREPL-29</link>
                <project id="10022" key="NREPL">tools.nrepl</project>
                        <description>&lt;p&gt;When specifying middleware, it would be much easier for the user to be able to override a default middleware without having to specify a handler.&lt;/p&gt;

&lt;p&gt;For example, if there is a default middleware providing the &quot;complete&quot; operation, the user should be able to just specify their preferred completion middleware, without having to specify all middleware as a handler.&lt;/p&gt;

&lt;p&gt;One way to do this might be to check metadata for the provided operations of the specified metadata, and ensure that either the default middleware for that operation is removed, or that the specified middleware takes precendence (which may be simpler when a middleware provides multiple operations).&lt;/p&gt;</description>
                <environment></environment>
            <key id="15687">NREPL-29</key>
            <summary>Provide a mechanism for overriding an operation</summary>
                <type id="4" iconUrl="http://dev.clojure.org/jira/images/icons/improvement.gif">Enhancement</type>
                                <priority id="3" iconUrl="http://dev.clojure.org/jira/images/icons/priority_major.gif">Major</priority>
                    <status id="1" iconUrl="http://dev.clojure.org/jira/images/icons/status_open.gif">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="cemerick">Chas Emerick</assignee>
                                <reporter username="hugoduncan">Hugo Duncan</reporter>
                        <labels>
                    </labels>
                <created>Sun, 9 Sep 2012 14:11:13 -0500</created>
                <updated>Tue, 13 Nov 2012 12:17:57 -0600</updated>
                                    <version>0.2.0-beta9</version>
                <version>0.2.0-beta10</version>
                                                        <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="29439" author="cemerick" created="Fri, 14 Sep 2012 07:44:39 -0500"  >&lt;p&gt;Agreed.&lt;/p&gt;

&lt;p&gt;Just making sure that the order in which additional middlewares are provided is taken as a default stack order will suffice for most use cases.  Transforming middlewares (either in full or in part) would need another metadata slot, &lt;tt&gt;:replace&lt;/tt&gt; perhaps, though it seems like that would be much more difficult to get right.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>