Undocumented Breaking Change: previously added null fields are gone

[IsaacLeeWebDev]

Is your proposal related to a problem?

There's an undocumented breaking change between Hasura v1.3.4 and v2.12.1 (I don't have the time to isolate it to a smaller range right now, but I may come back and update it if I can!)

Here's the v1.3.4 behavior when you send a GraphQL request containing an operation document selecting fields from a Hasura Action whose backing REST API omits one or more of those fields in the response:

Here's the v2.12.1 behavior:

As you can see, the "message": null field in the v1.3.4 response was removed after the upgrade.

While there's not a huge difference between "something": null and nothing at all, some folks may– for some wild reason I can't think of– depend on that old behavior.

Describe the solution you'd like

Document this breaking change in the change log, or v2 migration guide.

Describe alternatives you've considered

I guess patching the behavior is possible, but that would be another breaking change to different versions, so 🤷

[adas98012]

@rahulagarwal13

Related issue #9191 #8473

[rahulagarwal13]

@IsaacLeeWebDev - got it, thanks for bringing this up!