Attempt to support system-components (#292)

* Attempt to support system-components

This partially fixes #239

Will also require changes in react-docgen-annotation-resolver.

* Remove console.log

src/utils/__tests__/getMemberExpressionValuePath-test.js

@@ -73,6 +73,18 @@ describe('getMemberExpressionValuePath', () => {
         Foo.propTypes = {};
       `);
 
+      expect(getMemberExpressionValuePath(def, 'propTypes')).toBe(
+        def.parent.get('body', 1, 'expression', 'right'),
+      );
+    });
+  });
+  describe('CallExpression', () => {
+    it('finds "normal" property definitions', () => {
+      const def = statement(`
+        const Foo = system({is: "button"}, "space");
+        Foo.propTypes = {};
+      `);
+
       expect(getMemberExpressionValuePath(def, 'propTypes')).toBe(
         def.parent.get('body', 1, 'expression', 'right'),
       );

src/utils/__tests__/getMemberValuePath-test.js

@@ -50,6 +50,13 @@ describe('getMemberValuePath', () => {
     expect(getClassMemberValuePath).toBeCalledWith(path, 'foo');
   });
 
+  it('handles CallExpressions', () => {
+    const path = expression('system({is: "button"}, "space")');
+
+    getMemberValuePath(path, 'foo');
+    expect(getMemberExpressionValuePath).toBeCalledWith(path, 'foo');
+  });
+
   it('tries synonyms', () => {
     let path = expression('{}');
 

src/utils/getMemberExpressionValuePath.js

@@ -42,6 +42,7 @@ function resolveName(path) {
     types.FunctionExpression.check(path.node) ||
     types.ArrowFunctionExpression.check(path.node) ||
     types.TaggedTemplateExpression.check(path.node) ||
+    types.CallExpression.check(path.node) ||
     isReactForwardRefCall(path)
   ) {
     let currentPath = path;

src/utils/getMemberValuePath.js

@@ -54,7 +54,7 @@ function isSupportedDefinitionType({ node }) {
      * TaggedTemplateExpression's to generate components.
      *
      * While react-docgen's built-in resolvers do not support resolving
-     * TaggedTemplateExpression definitiona, third-party resolvers (such as
+     * TaggedTemplateExpression definitions, third-party resolvers (such as
      * https://github.com/Jmeyering/react-docgen-annotation-resolver) could be
      * used to add these definitions.
      */
@@ -64,6 +64,16 @@ function isSupportedDefinitionType({ node }) {
     types.ArrowFunctionExpression.check(node) ||
     types.FunctionDeclaration.check(node) ||
     types.FunctionExpression.check(node) ||
+    /**
+     * Adds support for libraries such as
+     * [system-components]{@link https://jxnblk.com/styled-system/system-components} that use
+     * CallExpressions to generate components.
+     *
+     * While react-docgen's built-in resolvers do not support resolving
+     * CallExpressions definitions, third-party resolvers (such as
+     * https://github.com/Jmeyering/react-docgen-annotation-resolver) could be
+     * used to add these definitions.
+     */
     types.CallExpression.check(node)
   );
 }
@@ -92,8 +102,7 @@ export default function getMemberValuePath(
         'VariableDeclaration, ArrowFunctionExpression, FunctionExpression, ' +
         'TaggedTemplateExpression, FunctionDeclaration or CallExpression. Got "' +
         componentDefinition.node.type +
-        '"' +
-        'instead.',
+        '" instead.',
     );
   }