roy-mor
roy-mor
Thanks @klinskyc. Can you add tests and explain the change and the use case(s)?
@klinskyc : can you explain this PR? Besides the conflicts that you need to resolve, can you please add minimal tests and documentation so that I can merge your contribution...
Since an empty JSON object may be seen as violating the "No Content" standard for 204 HTTP code, we should not ALWAYS return JSON responses. Therefore closing this PR without...
@mehmetnyarar Please open this PR on the correct repo, sisense/graphql2rest (you've opened it on a fork).
I confirm that the problem was with `object.inspect()` being deprecated. I replaced `inspect()` with `toJSON()` (which is more appropriate than `toString()` here). This issue was fixed by [PR #73 ](https://github.com/sisense/graphql2rest/pull/73)....
I don't have much capacity for it right now, maybe you can do it or perhaps @motigra / @yotamgever can assign someone interested.