From f6da4b13b86327e1d9e9ab781dd091cf5a868879 Mon Sep 17 00:00:00 2001
From: Hraban Luyat <hraban@0brg.net>
Date: Fri, 30 Jan 2015 06:02:33 +0100
Subject: [PATCH] Discern new vs old style components through render

By overloading createElement() for the ClassicComponentClass and
creating a separate ReactClassicElement type, we can keep track of which
calls to render() should create a ClassicComponent versus a new style
Component. Useful for keeping the old API, which makes migration easier.
---
 react/react-0.13.0.d.ts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/react/react-0.13.0.d.ts b/react/react-0.13.0.d.ts
index b5a1d1495..9ee102541 100644
--- a/react/react-0.13.0.d.ts
+++ b/react/react-0.13.0.d.ts
@@ -17,6 +17,9 @@ declare module React {
         ref: string;
     }
 
+    interface ReactClassicElement<P> extends ReactElement<P> {
+    }
+
     interface ReactHTMLElement extends ReactElement<HTMLAttributes> {}
     interface ReactSVGElement extends ReactElement<SVGAttributes> {}
 
@@ -112,8 +115,10 @@ declare module React {
 
     interface TopLevelAPI {
         createClass<P, S, C>(spec: ComponentSpec<P, S, C>): ClassicComponentClass<P, S, C>;
+        createElement<P>(type: ClassicComponentClass<P, any, any>, props: P, ...children: ReactNode[]): ReactClassicElement<P>;
         createElement<P>(type: ComponentClass<P, any, any> | string, props: P, ...children: ReactNode[]): ReactElement<P>;
         createFactory<P>(type: ComponentClass<P, any, any> | string): ComponentFactory<P>;
+        render<P, S>(element: ReactClassicElement<P>, container: Element, callback?: () => any): ClassicComponent<P, S, any>;
         render<P, S>(element: ReactElement<P>, container: Element, callback?: () => any): Component<P, S, any>;
         unmountComponentAtNode(container: Element): boolean;
         renderToString(element: ReactElement<any>): string;