Santino

Surely this can be baked into the `serve` command for convenience. However, in the meantime, you can simply implement this with [nodemon](https://github.com/remy/nodemon). You could take inspiration from the following command...

Thanks for raising this. It would be great if you could contribute to improving the documentation. Do you feel you would be able to raise a PR for this?

Hey @angelsvirkov, happy to read a conversation about feedback and potential improvements. Probably people watching this repo can share several thoughts on the points you have raised. But I wonder...

Hi @mbrowne , thanks for the codesandbox. I had a quick look. You're right, filtering out a field and then re-introducing it with additional type definitions seems to cause a...

The underlying issue is surely going to be complex and it won't necessarily be feasible to solve. If you filter out the `name` field from the schema, then it makes...

Hi @D1no, thank you very much for posting your repository, it is super useful. I have been debugging the issue and finding out the root cause. This is happening because...

Thanks for your comment. Just to bring some clarity I do contribute to this repository, but I am not part of the team that owns and maintains it, so I...

Thanks for your feedback @ntziolis. I understand it takes some time to learn the transform, because is very powerful and you can achieve a lot, the configuration has also several...

Thanks, @ntziolis. Reading your message makes me think that perhaps what you need is a different transform. Replace-field is there to override parts of the schema, where especially you want...

From my response above: > ... a "move-field" transform that is able to move and/or copy/duplicate fields from one Type to one or more Types across your schema. > That...