Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to open a project in Kamasi using the LearnDeep stack #74

Open
bhaugen opened this issue Sep 26, 2017 · 2 comments
Open

Trying to open a project in Kamasi using the LearnDeep stack #74

bhaugen opened this issue Sep 26, 2017 · 2 comments

Comments

@bhaugen
Copy link
Contributor

bhaugen commented Sep 26, 2017

I got logged in, can see list of 2 projects. When clicking on a project to see the details, I see Loading... forever, and these messages in the FireFox console:

"Download the React DevTools for a better development experience: https://fb.me/react-devtools"  ReactDOM.js:73:9
"Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in  React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs"  lowPriorityWarning.js:40:7
"Warning: fragment with name coreCommitmentFields already exists.
graphql-tag enforces all fragment names across your application to be unique; read more about
this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names"  index.js:48:11
"Warning: fragment with name coreEventFields already exists.
graphql-tag enforces all fragment names across your application to be unique; read more about
this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names"  index.js:48:11
[HMR] connected  client.js:82:22
Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) ct-empty: 2 --><div data-reactid="3"><st
 (server) ct-empty: 2 --><div class="c3hMsF" data-  warning.js:35:7
connected to remotedev-server  devTools.js:242:5
undefined singleprojectTemplate.js:44:5
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in. Check the render method of `StatelessComponent`.
    in Unknown (created by Apollo(Component))
    in Apollo(Component) (created by Connect(Apollo(Component)))
    in Connect(Apollo(Component)) (created by Unknown)
    in Unknown (created by Unknown)
    in Unknown (created by RouterContext)
    in div (created by SiteTemplate)
    in AuthenticatedOnly (created by Connect(AuthenticatedOnly))
    in Connect(AuthenticatedOnly) (created by SiteTemplate)
    in SiteTemplate (created by App)
    in div (created by App)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router
    in QueryRecyclerProvider (created by ApolloProvider)
    in ApolloProvider
    in AppContainer  warning.js:35:7
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in. Check the render method of `StatelessComponent`.  app.49d1c727520e0c2a6a80.js%20line%203769%20%3E%20eval:44:15
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead.  6
@bhaugen
Copy link
Contributor Author

bhaugen commented Sep 26, 2017

I installed the FireFox React dev tools but have no idea how to interpret them. @pospi @ivanminutillo if you want me to post any of the contents from the tool, let me know what.

@bhaugen
Copy link
Contributor Author

bhaugen commented Sep 26, 2017

I did this query in GraphiQL and worked fine. In other words, I don't think the problem is in graphql:

query ($token: String) {
  viewer(token: $token) {
    agent(id: 6) {
      name
      agentEconomicEvents {
        id
        action
        start
        affectedQuantity {
          numericValue
          unit {
            name
          }
        }
        affects {
          resourceClassifiedAs {
            name
            category
          }
          trackingIdentifier
        }
        provider {
          id
          name
        }
        receiver {
          id
          name
        }
        note
      }
      agentCommitments {
        id
        action
        plannedStart
        committedOn
        due
        committedQuantity {
          numericValue
          unit {
            name
          }
        }
        provider {
          id
          name
        }
        receiver {
          id
          name
        }
        note
      }
    }
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant