Description

Hasura was rendering strings and objects as the same in browse rows, we couldn't differentiate one from another.

Changelog

• CHANGELOG.md is updated with user-facing content relevant to this PR.

Affected components

• Server
• Console
• CLI
• Docs
• Community Content
• Build System
• Tests
• Other (list it)

Related Issues

#4201

Solution and Design

Checking if the column is a JSON or JSONB type instead of only if the value is an object fix the issue.

Before (You couldn't tell that one of the rows is a string by mistake):

After (You can see the difference clearly):

Steps to test and verify

Create one json and one jsonb columns, create two rows, one with both values as {"object":true} and another one with both values as "{\"string\": \"true\"}".

You can't tell the difference in Browse Rows before and you should after this fix.

Limitations, known bugs & workarounds

None.

Server checklist

None.

Catalog upgrade

Does this PR change Hasura Catalog version?

• No
• Yes
  • Updated docs with SQL for downgrading the catalog

Metadata

Does this PR add a new Metadata feature?

• No
• Yes
  • Does run_sql auto manages the new metadata through schema diffing?
    • Yes
    • Not required
  • Does run_sql auto manages the definitions of metadata on renaming?
    • Yes
    • Not required
  • Does export_metadata/replace_metadata supports the new metadata added?
    • Yes
    • Not required

GraphQL

• No new GraphQL schema is generated
• New GraphQL schema is being generated:
  • New types and typenames are correlated

Breaking changes

• No Breaking changes

• There are breaking changes:

  1. Metadata API

     Existing query types:

     • Modify args payload which is not backward compatible
     • Behavioural change of the API
     • Change in response JSON schema
     • Change in error code

  2. GraphQL API

     Schema Generation:

     • Change in any NamedType
     • Change in table field names

     Schema Resolve:-

     • Change in treatment of null value for any input fields

  3. Logging

     • Log JSON schema has changed
     • Log type names have changed