Closed kylecordes closed 7 years ago
To fully type an application using cyclic-router, I need to refer to the RouteMatcherReturn interface.
export interface RouteMatcherReturn { path: string; value: any; }
This currently requires ugly imports:
import { RouteMatcherReturn } from 'cyclic-router/lib/interfaces';
I think this interface should be re-export this from the facade, for simpler use from application code.
(Related: RouterSource.define currently returns type any - it's really a Stream<RouteMatcherReturn>, right?)
Stream<RouteMatcherReturn>
Can you submit a PR?
Yes... But I feel like I should use this router a bit more, to have confidence my changes are good. Will do.
@ntilwalli #194
To fully type an application using cyclic-router, I need to refer to the RouteMatcherReturn interface.
This currently requires ugly imports:
I think this interface should be re-export this from the facade, for simpler use from application code.
(Related: RouterSource.define currently returns type any - it's really a
Stream<RouteMatcherReturn>
, right?)