https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • c

    Callum

    01/11/2018, 7:17 AM
    would this not just add a (however small) step/request for my data to be retrierved
  • l

    lewisblackwood

    01/11/2018, 9:41 AM
    hey all 👋 I know that projects from pre-Graphcool framework era need to be ejected to work with the CLI tool now. But is it possible to download the
    yml
    file and
    types.graphql
    before ejecting (even if it's not possible to deploy back up to the project without ejecting)?
    • 1
    • 1
  • w

    weakky

    01/11/2018, 9:44 AM
    Hohai ; Ejecting your project will normally let you download a .zip file with all you need to launch that same project from CLI
  • w

    weakky

    01/11/2018, 9:45 AM
    It will for sure give you the yml file and types.graphql file you’re talking about, but I think it even generates you all the boilerplate generated with a > graphcool init. Your best try would be to clone your project on the console, and try ejecting that clone. See then what they give you to download
  • l

    lewisblackwood

    01/11/2018, 9:46 AM
    Ah that's a great shout @weakky - I'd totally forgotten you could clone a project. Will do that. Cheers!
  • p

    pokorson

    01/11/2018, 9:48 AM
    Hi, I have a problem with running local server, it looks that it starts correctly but when I go to web playground I get
    Copy code
    Schema could not be fetched.
    Please check if the endpoint '<http://localhost:60001/simple/v1/cjca93oop00040177e08qwxpr>' is a valid GraphQL Endpoint.
    n
    • 2
    • 2
  • l

    lkbr

    01/11/2018, 9:53 AM
    Hello, We are getting intermittent timeouts to the graph.cool API. We have not transitioned to the new cli based stuff. It's inconsistent so I'm struggling to test. Kinda new to GraphQL and API's in general so I'm wondering if anyone knows of a quick way or service to test API uptime, like pingdom, so we are atleast aware when issues are happening and can retrospectively look back. Thanks for any help.
  • k

    KTITS-Kevin

    01/11/2018, 10:30 AM
    Hello, if i execute an upsert with a connect inside (running 1.0 beta4) i get the following error: "Unsupported scalar value in SlickExtensions: Some(ListMap(connect -> Some(ListMap(id -> Some(cjc99y7q4006e0181fulirnrj)))))" If i run the upsert without the connect everything works fine.
    n
    • 2
    • 1
  • b

    Bartek

    01/11/2018, 10:54 AM
    Hello
  • b

    Bartek

    01/11/2018, 10:55 AM
    I executed
    graphql create graphcool --boilerplate react-fullstack-basic
    and have: `Couldn’t find
    graphcool.yml
    file. Are you in the right directory?` and
    Cannot read property 'httpEndpoint' of undefined
    , is this ok? 🙂
    👍 1
    j
    • 2
    • 3
  • l

    lewisblackwood

    01/11/2018, 11:07 AM
    Seeing 504 errors fairly often like on Tuesday - is there anything that can be done to improve this?
  • f

    fabien0102

    01/11/2018, 11:15 AM
    Hello, that I'm understanding from the 1.0 documentation, graphcool is now a database instead of a Baas (that means that I need to deal with a server…) what is the long-terme plan? have Baas and graphqlDb or only graphDb? (just to know if I need to reimplement a new server now or if it's safe to continue with the Bass (I'm quite lazy and prefer the Baas solution XD )
  • l

    lkbr

    01/11/2018, 11:15 AM
    504's too 😕
  • l

    lewisblackwood

    01/11/2018, 11:27 AM
    the console seems super slow too 😬
  • m

    matty

    01/11/2018, 12:00 PM
    @fabien0102 I think Graphcool will become the database+graphql technology, and "Graphcool Cloud" will provide the Baas hosting
    👌 1
  • k

    KTITS_Tom

    01/11/2018, 1:06 PM
    @nilan I have a mandatory field on graphcool's schema and want to set values (connect) in resolvers on webserver automatically. Is there a way to make these mandatory fields optional for the client?
  • j

    johannpinson

    01/11/2018, 1:19 PM
    hi @nilan, the online docs is again down 😕 (tested in FF Dev edition and Chrome for me)
  • d

    dohomi

    01/11/2018, 1:30 PM
    I also experience downtime of my instance. started today again and now the service is entirely down
  • l

    lkbr

    01/11/2018, 1:32 PM
    Still getting 504 timeouts and 502 bad gateways...
  • l

    lewisblackwood

    01/11/2018, 1:32 PM
    lots of 5XX errors and super slow responses too ☹️
  • l

    lewisblackwood

    01/11/2018, 1:33 PM
    did send an email to
    support@graph.cool
    a couple of hours ago
  • l

    lkbr

    01/11/2018, 1:33 PM
    Same.
  • m

    mlukaszczyk

    01/11/2018, 1:35 PM
    Can confirm for multiple projects as well
  • n

    nilan

    01/11/2018, 1:53 PM
    Thanks everyone, we're currently investiating degraded performance in the shared simple API: https://status.graph.cool/
    👍 5
  • n

    noahdavis

    01/11/2018, 2:04 PM
    Hey everyone! Looking for a solution for a very long running resolver. It hits multiple endpoints from my backend APIs and then does some computation.
  • n

    noahdavis

    01/11/2018, 2:04 PM
    What's the best way to handle this in order to avoid the timeout limit?
  • n

    noahdavis

    01/11/2018, 2:20 PM
    Looking for a step functions solution
  • n

    noahdavis

    01/11/2018, 2:21 PM
    ex. Serverless framework step functions
  • p

    patrick

    01/11/2018, 3:15 PM
    @nilan are the docs offline too? can’t seem to load the page https://www.graph.cool/docs
  • h

    harmony

    01/11/2018, 3:17 PM
    seems like it :/
1...501502503...637Latest