vetcher
vetcher
Your problems is actually bug #13 and I does not know right way, how to fix it
The problem is in `UserID int32`. By graphql spec ID is a string. Changing type to graphql.ID should fix your problem Or change the schema to ```graphql type LifeBalance {...
You should not use graphql.ID as your primary key in db. Just extract string from this type and use it as your wish (as uuid or convert to int, idk)
yea, error messages are disgusting
what's golang version you use?
@pavelnikolov definitely
Problem in manipulating with ast is that it binded to FileSet and adding some nodes to existing tree is hard to work and render properly. Idk how to add to...
Oh, it will be great. But anyway I will fork this one and make all what I mention in topic, because right now it's an easiest way to render imports...
@vzool Hi. I think, the main reason, why it panics, because you use pointers in Update method. Could you post minimal example, that panics on https://play.golang.org ? In current implementation,...