[Wip] master stateless overload #13640

yuit · 2017-01-23T19:56:19Z

Update of the previous PR #12107

Fix: #11187 (see: tsxSpreadAttributesResolution1.tsx), #9703 (see : tsxStatelessFunctionComponentOverload6.tsx)

Overview of the change

Treat JSXAttributes similar to ObjectLiteralExpression. We change the AST structure and store JSXAttributes as a AST Node instead of NodeArray
Using overload resolution logic in choosing signature of stateless function component

Note
Currently when we see spread of any type, the entire attributes has any type which means that follow example is allowed even though we should give an error:

declare function MainBuntton(attr1: {to: string}): JSX.Element;
declare function MainBuntton(attr2: {onClick: ()=> void}): JSX.Element;
declare var obj3: any;
const b = <MainBuntton {...obj3} to={10} />;  // should error for mismatched type

… array # Conflicts: # src/compiler/visitor.ts

Add language service support for JSXAttributes Add completion support Add find-all-references support Add goto-definition support

…onent

…lue to map

…alType property directly

Address comment: using ternary operator, fix comments

…AttributesTypeFromAttributesProperty

Address comment: fix spelling mistakes Address comment: calling `checkApplicableSignatureForJsxOpeningLikeElement` from inside `checkApplicableSignature` Address comment: fix spelling, rename function to be more consistent Address comment: minor fix indentation, fix function name isObjectLiteralPropertyDeclaration => isObjectLiteralElement Address PR: gotoDefinition return the last signature when there is an error in statelss function component Address PR: convert Foreach to for...of Address comment: fix type, inline code, clarify name of variables

… failure to resolve signature cases

sandersn

A few comments before looking at the checker and services code.

sandersn · 2017-01-27T22:45:40Z

src/compiler/types.ts

@@ -2697,6 +2702,7 @@
        /* @internal */ isReferenced?: boolean; // True if the symbol is referenced elsewhere
        /* @internal */ isReplaceableByMethod?: boolean; // Can this Javascript class property be replaced by a method symbol?
        /* @internal */ isAssigned?: boolean;   // True if the symbol is a parameter with assignments
+        /* @internal */ syntheticKind?: SyntheticSymbolKind; // Synthetic symbols are either spread or union/intersection


This isn't used anymore, so you should remove this line. I forgot to remove SyntheticSymbolKind itself, but I'll do that in the spread-type PR. #Closed

sandersn · 2017-01-27T22:47:01Z

src/compiler/emitter.ts

@@ -1824,15 +1826,21 @@ namespace ts {
            write("<");
            emitJsxTagName(node.tagName);
            write(" ");
-            emitList(node, node.attributes, ListFormat.JsxElementAttributes);
+            // We are checking here so we won't re-enter the emiting pipeline and emit extra sourcemap


typo: emiting → emitting

sandersn · 2017-01-27T22:53:22Z

src/compiler/emitter.ts

-            writeIfAny(node.attributes, " ");
-            emitList(node, node.attributes, ListFormat.JsxElementAttributes);
+            writeIfAny(node.attributes.properties, " ");
+            // We are checking here so we won't re-enter the emiting pipeline and emit extra sourcemap


Can you give an example when this would happen?

I will confirm with Ron. My understanding is that we only want to call emit if the attributes are not empty (as this can cause extra sourcemap)

sandersn

Comments from reviewing checker

sandersn · 2017-01-27T23:25:31Z

src/compiler/checker.ts

-                    if ((relation === assignableRelation || relation === comparableRelation) && (type === globalObjectType || isEmptyObjectType(resolved)) ||
-                        resolved.stringIndexInfo ||
-                        (resolved.numberIndexInfo && isNumericLiteralName(name)) ||
-                        getPropertyOfType(type, name)) {


Would it be equivalent just to add a line || (isComparingJsxAttributes && !isUnhyphenatedJsxName(name))) to the original code? If that's the case, I'd just do that. I think it's easier to read as a compact series of cases that return true.

sandersn · 2017-01-27T23:48:29Z

src/compiler/checker.ts

+                                    reportError(Diagnostics.Property_0_does_not_exist_on_type_1, symbolToString(prop), typeToString(target));
+                                }
+                                else {
+                                    errorNode = prop.valueDeclaration;


Do errors get more precise if you set errorNode = prop.valueDeclaration ? I noticed that the error spans the entire JSX literal currently.

If that change works, then I would also suggest pushing the isJsxAttributes predicate down inside the reportError call since the other arguments are the same for both branches. #Resolved

Talk offline, the error message helps elaborate this further so it should be ok for now.

sandersn · 2017-01-27T23:58:10Z

src/compiler/checker.ts

+            // When we trying to resolve JsxOpeningLikeElement as a stateless function element, we will already give its attributes a contextual type
+            // which is a type of the parameter of the signature we are trying out.
+            // If there is no contextual type (e.g. we are trying to resolve stateful component), get attributes type from resolving element's tagName
+            const attributesType = getContextualType(<Expression>attribute.parent) || getAttributesTypeFromJsxOpeningLikeElement(<JsxOpeningLikeElement>attribute.parent.parent);


getContextualType calls getAttributesTypeFromJsxOpeningLikeElement(parent) for JsxOpeningLikeElement, so when you call getContextualType(attribute.parent) shouldn't it be equivalent to getAttributesTypeFromJsxOpeningLikeElement(<JsxOpeningLikeElement>attribute.parent.parent)? If so, you can call only getContextualType here. #Closed

sandersn · 2017-01-28T00:05:59Z

src/compiler/checker.ts

+        }
+
+        /**
+         * Get the attributes type which is the type that indicate which attributes are valid on the given JSXOpeningLikeElement.


The jsdoc tags here are low-value -- they just restate the type and function names.

I would rewrite the description as "Get the attributes type, which indicates the attributes that are valid on the given JSXOpeningLikeElement." #Closed

sandersn · 2017-01-28T00:12:08Z

src/compiler/checker.ts

+        /**
+         * Get attributes type of the given custom opening-like JSX element.
+         * This function is intended to be called from a caller that handles intrinsic JSX element already.
+         * @param node a custom JSX opening-like element


same here, the param tag doesn't have interesting information and there is no tag for shouldIncludeAllStatelessAttributesType, which is the more mysterious one since its type is just boolean. #Closed

The comment above the call from getAllAttributesType... is a good candidate for explaining the boolean. #Closed

sandersn · 2017-02-01T18:59:45Z

src/compiler/checker.ts

@@ -12218,7 +12443,7 @@ namespace ts {
            return jsxElementClassType;
        }

-        /// Returns all the properties of the Jsx.IntrinsicElements interface
+        // Returns all the properties of the Jsx.IntrinsicElements interface


might as well turn this into jsdoc while you're here #Closed

sandersn · 2017-02-01T19:00:44Z

src/compiler/checker.ts

-                    }
-                }
-            }
+            checkJsxAttributesAssignableToTagNameAttributes(node);


can you move the definition of this function closer to its call? #Closed

sandersn · 2017-02-01T19:17:37Z

src/compiler/checker.ts

@@ -12744,6 +12940,13 @@ namespace ts {
            let isDecorator: boolean;
            let spreadArgIndex = -1;

+            if (isJsxOpeningLikeElement(node)) {
+                // For JSX opening-like element, we will ignore regular arity check (which is what is done here).


can you make this comment shorter? Basically just give a link to the function that does the work instead: "The arity check will be done in checkApplicableSignatureForJsxOpeningLikeElement instead". #Closed

sandersn · 2017-02-01T19:24:33Z

src/compiler/checker.ts

+            // However "context" and "updater" are implicit and can't be specify by users. Only the first parameter, props,
+            // can be specified by users through attributes property.
+            const paramType = getTypeAtPosition(signature, 0);
+            const argType = checkExpressionWithContextualType(node.attributes, paramType, /*contextualMapper*/ undefined);


I think attributesType is a better name. #Closed

sandersn · 2017-02-01T19:38:05Z

src/compiler/checker.ts

@@ -13422,6 +13669,11 @@ namespace ts {
                // in arguments too early. If possible, we'd like to only type them once we know the correct
                // overload. However, this matters for the case where the call is correct. When the call is
                // an error, we don't need to exclude any arguments, although it would cause no harm to do so.
+                if (isJsxOpeningOrSelfClosingElement) {
+                    // If there is not result, just return the last one we try as a candidate.


It looks like this if should go before the preceding comment block that talks about excludeArgument.

I would delete the first line of the comment because it just repeats what the code itself says. #Closed

sandersn

Comments from services side.

sandersn · 2017-02-01T22:27:15Z

src/services/goToDefinition.ts

+            //      /*secondSource*/declare function MainButton(linkProps: LinkProps): JSX.Element;
+            //      /*thirdSource*/declare function MainButton(props: ButtonProps | LinkProps): JSX.Element;
+            //      let opt = <Main/*firstTarget*/Button />;  // We get undefined for resolved signature indicating an error, then just return the first declaration
+            const {symbolName, symbolKind, containerName}  = getSymbolInfo(typeChecker, symbol, node);


double-space before the equals sign. Does the linter catch this? #Closed

Nop, the linter doesn't catch it .we should fix the linter though. I fix this space in my commit

sandersn · 2017-02-01T22:28:17Z

src/services/goToDefinition.ts

+            // For JSX opening-like element, the tag can be resolved either as stateful component (e.g class) or stateless function component.
+            // Because if it is a stateless function component with an error while trying to resolve the signature, we don't want to return all
+            // possible overloads but just the first one.
+            // For example:


This example didn't help my understanding. #Closed

From in-person discussion, the comment is wrong now and needs to be updated. #Closed

sandersn · 2017-02-01T23:05:36Z

src/services/symbolDisplay.ts

                    if (!signature && candidateSignatures.length) {
                        // Use the first candidate:
                        signature = candidateSignatures[0];
                    }

-                    const useConstructSignatures = callExpression.kind === SyntaxKind.NewExpression || callExpression.expression.kind === SyntaxKind.SuperKeyword;
+                    let useConstructSignatures = false;


I liked the single-expression form better.

Did you add isCallExpression because of this change? super doesn't seem related to stateless JSX overload resolution. #Closed

Yep because callExpressionLike include JSXOpeningElement as well. I did fix it up to use single-expression

sandersn

Comments from the test

sandersn · 2017-02-01T23:35:12Z

tests/baselines/reference/contextuallyTypedStringLiteralsInJsxAttributes02.errors.txt

+        return this._buildMainButton(props);
+    }
+
+    const b0 = <MainButton {...{onClick: (k) => {console.log(k)}}} extra />;  // k has type any


I don't think the comment is correct; k should have the type 'left' | 'right' #Closed

ah. I fix the contextual type and forgot to update the comment. Thanks

sandersn · 2017-02-02T00:19:38Z

tests/baselines/reference/tsxAttributeResolution3.errors.txt

+           ~~~~~~~~~~~~~~~~
+!!! error TS2322: Type '{ x: number; y: number; }' is not assignable to type 'Attribs1'.
+!!! error TS2322:   Types of property 'x' are incompatible.
+!!! error TS2322:     Type 'number' is not assignable to type 'string'.

    // OK


this should not be Error (extras not allowed)

what do you mean? Do you mean on <test1 {...obj6} />?

Sorry, I meant should be. Right the comment is // OK but <test1 {...obj6} /> actually causes an error.

sandersn · 2017-02-02T00:21:00Z

tests/baselines/reference/tsxAttributeResolution5.errors.txt

@@ -23,26 +23,26 @@ tests/cases/conformance/jsx/file.tsx(30,1): error TS2324: Property 'toString' is

    function make1<T extends {x: string}> (obj: T) {
    	return <test1 {...obj} />; // OK
+    	              ~~~~~~~~
+!!! error TS2698: Spread types may only be created from object types.


these baselines will change back to OK after spread types are merged, which might be before this PR or might be after.

sandersn · 2017-02-02T21:14:11Z

tests/baselines/reference/tsxStatelessFunctionComponents1.errors.txt

+      Type '42' is not assignable to type 'string'.
+tests/cases/conformance/jsx/file.tsx(26,15): error TS2322: Type '{ naaaaaaame: "no"; }' is not assignable to type 'IntrinsicAttributes & { name?: string; }'.
+  Property 'naaaaaaame' does not exist on type 'IntrinsicAttributes & { name?: string; }'.
+tests/cases/conformance/jsx/file.tsx(31,23): error TS2322: Type '{}' is not assignable to type 'IntrinsicAttributes & { "prop-name": string; }'.


The reason the error is missing extra-prop-name is that it's a hyphenated name, right?

yep. So the "extra-prop-name" doesn't exist in attribute type so it doesn't participate in the type check and get filter out

sandersn · 2017-02-02T21:59:45Z

tests/baselines/reference/tsxSpreadAttributesResolution6.errors.txt

+
+    // Error
+    let x = <TextComponent editable={true} />
+             ~~~~~~~~~~~~~


This particular error should go away when spread types are available, I think.

ah this error is related to this bug #13526

sandersn · 2017-02-02T22:01:26Z

tests/baselines/reference/tsxSpreadAttributesResolution7.errors.txt

+
+    let y1 = <TextComponent {...textPropsFalse} />
+              ~~~~~~~~~~~~~
+!!! error TS2600: JSX element attributes type '({ editable: false; } & { children?: ReactNode; }) | ({ editable: true; onEdit: (newText: string) => void; } & { children?: ReactNode; })' may not be a union type.


same here; after spread types are available, these errors will go away and may expose others.

sandersn · 2017-02-02T22:05:29Z

tests/baselines/reference/tsxSpreadAttributesResolution7.symbols

@@ -0,0 +1,62 @@
+=== tests/cases/conformance/jsx/file.tsx ===


there shouldn't be an *.errors.txt and a *.symbols + *.js. Which is correct?

errors.txt. I am surprised the test doesn't fail. Remove the symbols and types

sandersn · 2017-02-02T23:14:57Z

tests/cases/fourslash/tsxQuickInfo6.ts

+
+verify.quickInfos({
+    1: "function ComponentSpecific<{}>(l: {\n    prop: {};\n}): any",
+    2: "function ComponentSpecific<{}>(l: {\n    prop: {};\n}): any"


Why is U={} and the return type any instead of JSX.Element? Is the lack of spread types causing errors in the code?

The reason it is "any" because we will fail to get JSX.Element (as there is no react library loaded here)....I believe that U={} is due to lack of spread types.

sandersn · 2017-02-02T23:18:43Z

tests/cases/fourslash/tsxSignatureHelp1.ts

+//// export function MainButton(props: ButtonProps): JSX.Element {
+////     return this._buildMainButton(props);
+//// }
+//// let e1 = <MainButton/*1*/ /*2*/


what is the difference between /*1*/ and /*2*/ here? They look like they should be the same, and in fact they are.

~~you are right. I fix that~~ Just realize why I did that because I want to make sure we will show signature help both when we are on the tagName and empty attributes

sandersn · 2017-02-02T23:20:45Z

tests/cases/fourslash/tsxSignatureHelp2.ts

+//// let e1 = <MainButton/*1*/ /*2*/
+
+goTo.marker("1");
+// The second overload is chosen because the first doesn't get selected by choose overload as it has incorrect arity


This comment seems wrong, because it looks like the first overload is chosen after all.

you are right. the comment is not. I must have forgot to update it when I was experimenting

yuit · 2017-02-04T00:19:38Z

🔔 @RyanCavanaugh if you would like to give another look :)

yuit · 2017-02-06T17:49:11Z

Talk with @RyanCavanaugh, we should have better name for this one defaultTryGetJsxStatelessFunctionAttributesType

RyanCavanaugh · 2017-02-06T17:35:37Z

src/compiler/checker.ts

@@ -590,7 +590,7 @@ namespace ts {
            return node.kind === SyntaxKind.SourceFile && !isExternalOrCommonJsModule(<SourceFile>node);
        }

-        function getSymbol(symbols: SymbolTable, name: string, meaning: SymbolFlags): Symbol {
+       function getSymbol(symbols: SymbolTable, name: string, meaning: SymbolFlags): Symbol {


Wrong indent?

RyanCavanaugh · 2017-02-06T17:36:54Z

src/compiler/checker.ts

@@ -3362,6 +3362,11 @@ namespace ts {
                const type = checkDeclarationInitializer(declaration);
                return addOptionality(type, /*optional*/ declaration.questionToken && includeOptionality);
            }
+            else if (isJsxAttribute(declaration)) {


No need for else here

RyanCavanaugh · 2017-02-06T17:49:43Z

src/compiler/checker.ts

+                    return false;
+                }
+            }
+            if (checkTypeRelatedTo(attributesType, paramType, relation, /*errorNode*/ undefined, headMessage)) {


Can just return this value directly

RyanCavanaugh · 2017-02-06T17:50:32Z

src/compiler/checker.ts

@@ -13105,8 +13349,11 @@ namespace ts {
                // `getEffectiveArgumentCount` and `getEffectiveArgumentType` below.
                return undefined;
            }
+            else if (isJsxOpeningLikeElement(node)) {
+                args = node.attributes.properties.length > 0 ? [node.attributes] : [];


Intentional to use [] instead of emptyArray here?

RyanCavanaugh · 2017-02-06T17:53:17Z

src/compiler/checker.ts

+                let result: Signature;
+                for (const type of types) {
+                    // This is mainly to fill in all the candidates if there is one.
+                    result = result && resolveStatelessJsxOpeningLikeElement(openingLikeElement, type, candidatesOutArray);


Shouldn't this be || ? I would expect a failing test because of this

We don't have test around this surprisingly. I am adding one in

# Conflicts: # src/compiler/factory.ts

Kanchalai Tanglertsampan added 25 commits January 18, 2017 15:05

Parse JSX attributes as its own unique AST node and bind the node

5558406

Use chooseOverload logic to pick JSX stateless function

4671685

Update emitter to use JSXAttributes node instead of JSXAttribute node…

41108db

… array # Conflicts: # src/compiler/visitor.ts

Add language service support for JSXAttributes

16d1b5d

Add language service support for JSXAttributes Add completion support Add find-all-references support Add goto-definition support

Update existed conformance tests

d9927d4

Add tests for using spread attributes resolution in JSX stateful comp…

aea7d09

…onent

Add tests for using default attributes in JSX stateful component

b0fd66d

Add tests for overload stateless function component

9e3da08

Add tests for generic stateless function component

19d0548

Add a test for contextual type in JSXAttributes

70ca18e

Update react.d.ts used during tests

8ce7e37

Cache react.d.ts library when running tests

a0b7c2e

Update conformance tests baselines

2c15eab

Add language service tests

3d19782

Fix linting error

a44c3f2

Update calling to getSpreadType and using set function when adding va…

a39f9ef

…lue to map

Update baselines

2fd5667

Address comment: call getContextualType instead of accessing contextu…

350f47a

…alType property directly

Address comment: stop widen type when checking for spread any;

6ce31d7

Address comment: using ternary operator, fix comments

Refactor getJsxAttributeSymbolsFromJsxOpeningLikeElement to createJsx…

747ab05

…AttributesTypeFromAttributesProperty

Handle inference of function expression/arrow functions attribute

0b4f25c

Add tests and update baselines

378f444

Report an error when can't infer but do not report an error for other…

0ea5073

… failure to resolve signature cases

Update comments

a0cdc9d

msftclas added the cla-not-required label Jan 23, 2017

yuit requested review from sandersn, RyanCavanaugh and mhegazy January 23, 2017 19:56

yuit changed the title ~~Wip master stateless overload~~ [Wip] master stateless overload Jan 24, 2017

Update baselines from merging

fa56933

sandersn reviewed Jan 27, 2017

View reviewed changes

Kanchalai Tanglertsampan added 2 commits January 31, 2017 11:11

Address PR: fix typo

ceb7720

Merge branch 'master' into wip-master-statelessOverload

42c0816

sandersn reviewed Feb 1, 2017

View reviewed changes

Address code review

aea551c

sandersn requested changes Feb 2, 2017

View reviewed changes

Address code review

56f31c3

sandersn approved these changes Feb 3, 2017

View reviewed changes

Address code review: fix comment

bb7dea1

RyanCavanaugh requested changes Feb 6, 2017

View reviewed changes

Kanchalai Tanglertsampan added 7 commits February 8, 2017 17:19

Fix comments

2e8f16b

Correctly handle union of JSX element type

d8936e9

Add conformance tests for union element type

328f5cc

correctly handle the case when attributes type is empty object

e90a328

Add tests and baselines for union element type

d0dcee0

Add language service test when element type is a union type

6dec0f5

Update comment

e9a578c

yuit mentioned this pull request Feb 13, 2017

[Wip] Fix 11566 : allow null return in SFC #14045

Closed

RyanCavanaugh approved these changes Feb 14, 2017

View reviewed changes

Kanchalai Tanglertsampan added 2 commits February 14, 2017 15:21

Merge branch 'master' into wip-master-statelessOverload

e5cfe5c

# Conflicts: # src/compiler/factory.ts

Update baseline adding of "__esModule"

a52ccff

yuit merged commit ca6f1c3 into master Feb 15, 2017

yuit mentioned this pull request Feb 27, 2017

Treating attribute in JSX as literal type #10393

Closed

yuit deleted the wip-master-statelessOverload branch May 9, 2017 16:04

ghost mentioned this pull request Feb 8, 2018

Fix bug: Don't skip emitting JSX attributes #21777

Merged

microsoft locked and limited conversation to collaborators Jun 19, 2018

		@@ -0,0 +1,62 @@
		=== tests/cases/conformance/jsx/file.tsx ===

[Wip] master stateless overload #13640

[Wip] master stateless overload #13640

Conversation

yuit commented Jan 23, 2017 • edited Loading

sandersn left a comment

Choose a reason for hiding this comment

sandersn Jan 27, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sandersn left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sandersn Jan 27, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sandersn Jan 27, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Jan 28, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Jan 28, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Jan 28, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn left a comment

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

yuit Feb 2, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sandersn left a comment

Choose a reason for hiding this comment

sandersn Feb 1, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuit Feb 3, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuit Feb 3, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuit Feb 3, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuit Feb 3, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuit commented Feb 4, 2017

yuit commented Feb 6, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yuit commented Jan 23, 2017 •

edited

Loading

sandersn Jan 27, 2017 •

edited

Loading

sandersn Jan 27, 2017 •

edited

Loading

sandersn Jan 27, 2017 •

edited

Loading

sandersn Jan 28, 2017 •

edited

Loading

sandersn Jan 28, 2017 •

edited

Loading

sandersn Jan 28, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

yuit Feb 2, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

sandersn Feb 1, 2017 •

edited

Loading

yuit Feb 3, 2017 •

edited

Loading

yuit Feb 3, 2017 •

edited

Loading

yuit Feb 3, 2017 •

edited

Loading

yuit Feb 3, 2017 •

edited

Loading

yuit Feb 8, 2017 •

edited

Loading