Query/Mutation receives args object with a null prototype

This bug report should include:

• A short, but descriptive title. The title doesn’t need “Apollo” in it.
• The package name and version of Apollo showing the problem.
• [O] If applicable, the last version of Apollo where the problem did not occur.
• The expected behavior.
• The actual behavior.
• A simple, runnable reproduction!

Version: latest apollo-server-core (2.8.1)

Related SO

https://stackoverflow.com/questions/53983315/is-there-a-way-to-get-rid-of-object-null-prototype-in-graphql

Actual behavior

This has been discussed on SO, but the solution is less than ideal. Serializing things through json is silly overhead. If anything it is confusing and undefined/undocumented behavior. I’m filing this as a bug since a mutation should get an object passed in with a prototype. A query receives an args object with a prototype. This behavior should at least be made consistent and ideally an object with a prototype.

Example code:

	Mutation: {
		create: async (_, args, context, info) => {
			console.log(args.thing);
		},
	},

Output:

[Object: null prototype] {
    id: '00112233445566'
}

Expected behavior

{
    id: '00112233445566'
}

Current workaround

console.log(JSON.parse(JSON.stringify(args.thing)))

[glasser]

FWIW, I’m pretty sure this is a feature. It means that you can have args with names like toString and constructor and such without them being treated specially.

[quinten1333]

I made a simple library to fix this. The library is faster than going to json and back because it works in place. Link: https://www.npmjs.com/package/normalize-object-inheritance