Do you guys have any plans to make local developme...
# prisma-whats-news
Steven Sacks
03/08/2018, 2:33 PMDo you guys have any plans to make local development any easier?
Steven Sacks
03/08/2018, 2:34 PMFirst and foremost, it can take 20 seconds to deploy any code change.
Steven Sacks
03/08/2018, 2:35 PMSecond, the graph.cool logs are pretty terrible. All of the console.logs() get output into a single string with
\nJSON.stringify(anyObject)\nSteven Sacks
03/08/2018, 2:36 PMNo good very bad development experience. 😕
Steven Sacks
03/08/2018, 2:37 PMConsidering the vast majority of development time is spent doing this, and not having a perfectly working environment, it seems like engineering the logs to only be useful when everything is working with only the occasional issue is a bad idea.
Steven Sacks
03/08/2018, 2:38 PMI have to be honest and say that my experience developing against graph.cool locally has been pretty awful.
Steven Sacks
03/08/2018, 2:38 PMAnd it's been months and nothing has improved as far as I can tell to address local development.
e
etx
03/08/2018, 2:48 PMyou can use util.inspect
s
Steven Sacks
03/08/2018, 2:52 PMThat's hardly the primary issue
Steven Sacks
03/08/2018, 2:53 PMIt's still buried in a giant "paragraph" of other stuff surrounded by `\n`s everywhere
Steven Sacks
03/08/2018, 2:53 PMUnless I'm expected to only log one thing at a time
Steven Sacks
03/08/2018, 2:53 PMWhich is unacceptable.
Steven Sacks
03/08/2018, 2:54 PMI mean, maybe backend developers are used to horrible log environments where you have to write your own parsers to deal with the noise. I'm a front end developer. We have great debugging environments.
f
Futurekam
03/08/2018, 4:20 PMIsn’t it open source? You could make a PR :D
n
nilan
03/08/2018, 4:47 PMThanks for bringing this up, @Steven Sacks! I totally agree with your observations, local development can be more complicated than expected. Especially with the sometimes hidden assumptions that Graphcool Functions bring to the table (like the strict requirements for input/output).
Our developers are looking for ways to improve this experience. However, as we're using AWS Lambda under the hood, this is actually quite a difficult problem to crack.
If you have a function heavy development workflow, you might have a better experience using tools like serverless. I also encourage you to explore Prisma, which gives you a much better local development experience, in terms of logging and debugging.
4 Views