<p dir="auto">The generated docs of typescript files don't show the type of class and interface members.</p>
<p dir="auto">Currently having an <code class="notranslate">@Input</code> on a directive / component with the same as a native property name will shadow input binding (that it, a directive will get the bound value, not the native element). Apparently different rules apply to <code class="notranslate">@Output</code>s.</p>
<p dir="auto">In this plunker <a href="https://plnkr.co/edit/TDCsPTWeRvgALildXmkt?p=preview" rel="nofollow">https://plnkr.co/edit/TDCsPTWeRvgALildXmkt?p=preview</a> there is a component with the <code class="notranslate">change</code> output. It turns out that adding <code class="notranslate">(change)</code> event handler to this component will pick up bubbling <code class="notranslate">chnage</code> events which I find surprising / inconsistent with rules in place for <code class="notranslate">@Input</code>s.</p>
<p dir="auto">I wonder if the the current behavior is correct and steams from the conscious design decision? Or rather a side effect of the existing implementation?</p>