# prisma-whats-new
- s
schickling
08/09/2016, 10:01 AMHey @meghaphone! Welcome to our Slack 🙌 Please let us know if you need any help! - a
akre54
08/10/2016, 6:02 PMHey @schickling, the latest babel-plugin-react-relay bump broke our build. Do you have any suggestions for how to fix? - a
akre54
08/10/2016, 6:03 PMUnfortunately using a URL endpoint is impossible because our graphql server is behind cookie authentication - a
akre54
08/10/2016, 6:04 PMwe could conceivably hack a special token to allow auth, but I’d rather avoid that if I can - s
schickling
08/10/2016, 6:04 PMHi @akre54! Sorry about the inconveniences. - a
akre54
08/10/2016, 6:04 PMno worries 🙂 thanks for the project in the first place - s
schickling
08/10/2016, 6:04 PMYou should be able to set the cookie via the
configuration optionheaders - a
akre54
08/10/2016, 6:05 PMI’d rather avoid adding a backdoor into our auth because of the potential complications - a
akre54
08/10/2016, 6:05 PMwhat was the reason the graphql-js / schema option was removed? - a
akre54
08/10/2016, 6:06 PMI looked into graphql-config. shouldn’t it be possible to do what the plugin used to do? - s
schickling
08/10/2016, 6:06 PMThe babel plugin is now based on this project: https://github.com/graphcool/graphql-config - a
akre54
08/10/2016, 6:06 PMright. It looks like the logic was extracted from the plugin, but with the schema option dropped - a
akre54
08/10/2016, 6:06 PMwhich we were relying on - s
schickling
08/10/2016, 6:07 PMThis enables you to use the same way of configuration for multiple tools - s
schickling
08/10/2016, 6:07 PMWouldn't the cookie option be a way for you? - a
akre54
08/10/2016, 6:08 PMunfortunately no. Our sessions are tied to a foreign SAML server. - a
akre54
08/10/2016, 6:09 PMI could conceivably create a cookie called “GraphQL” and special-case for it. but it seems like a lot of work with potentially lots of dependencies to support - a
akre54
08/10/2016, 6:09 PMWhat was wrong with this previous version? https://github.com/graphcool/babel-plugin-react-relay/commit/ea5d779bf4a98f7dab7ce2d1adc73c2f3eec03de#diff-1fdf421c05c1140f6d71444ea2b27638L40 - a
akre54
08/10/2016, 6:09 PMit seems like the new architecture is more friendly to promises, no? - s
schickling
08/10/2016, 6:10 PMYeah, I can see that. - s
schickling
08/10/2016, 6:11 PMSo here is an idea: How about you'd do a PR adding support for graphql-js to graphql-config? That would automatically enable this feature for all tools using graphql-config. - a
akre54
08/10/2016, 6:13 PMSure thing. That was my original thought, but I wondered if there was a reason support was dropped in the first place. Is there a reason to drop it? (I was thinking maybe there were complications?) - s
schickling
08/10/2016, 6:13 PMWe basically wanted to keep the footprint rather small, but the project has a dependency on graphql-js anyway, so that shouldn't be a problem 🙂 - s
schickling
08/10/2016, 6:14 PMRight now, we're just not using it and didn't invest the time in building it as of now. - a
akre54
08/10/2016, 6:14 PMdo you guys use the server route, or are you building out the json? - a
akre54
08/10/2016, 6:15 PMI wouldn’t mind saving the schema.graphql and schema.json files again if I could automate it - a
akre54
08/10/2016, 6:15 PMone of the main reasons I switched to this project is so that I wouldn’t have to fiddle with all that - s
schickling
08/10/2016, 6:16 PMFeel free to create a PR to graphql-config. Shouldn't be hard actually 🙂 - a
akre54
08/10/2016, 6:19 PMdo you have the schema.js file that was used to create the schema.js file? - s
schickling
08/10/2016, 6:20 PMNot sure if I'm getting the question...