add computed fields support on console

[rikinsk]

Description

Add support for adding computed fields via the console

TODO

• verify migrations

Affected components

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

Related Issues

#3203 #3565

Solution and Design

Steps to test and verify

Limitations, known bugs & workarounds

Server checklist

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

[netlify]

Deploy preview for hasura-docs ready!

Built with commit 1f544d9

https://deploy-preview-3522--hasura-docs.netlify.com

[hasura-bot]

Review app for commit 8cc5387 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-8cc53871

[hasura-bot]

Review app for commit f7a39af deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-f7a39af9

[hasura-bot]

Review app for commit abdd967 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-abdd9674

[hasura-bot]

Review app for commit 574248f deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-574248fa

[hasura-bot]

Review app for commit 713126b deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-713126b5

[hasura-bot]

Review app for commit edd4bbc deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-edd4bbc5

[santicomp2014]

@rikinsk Hey nice job with this PR, I was wondering if this affected the computed field and roles.
Currently, I'm using a computed field, but when I query from a role it does not even appear as a field in the console neither from my frontend.

Should I create a new Issue?.
Thanks.

[darknoon]

Hey, this is really awesome and would fix one of my main gripes at the moment, which is creating views on my tables so I can add a computed field. My use case is signing URLs for S3 access, eg profile photo etc.

In the design, I think it would be clearer if the "function definition" area didn't show up until a matching function was found. I tried to start typing there, and took a sec to realize I needed to type in the exact name of the function.

What about a dropdown of existing functions?

Anyway, looking forward to using this!

[lexi-lambda]

• SERVER: The metadata has been updated to track the hdb_computed_field_function view. Catalog migrations need to be figured out.

Interesting issue—we basically need an “empty” migration, just to get the metadata migrations to fire. That shouldn’t be difficult to do, and in fact it’s probably simplest to genuinely just create an empty SQL file for the migration, which I think should work? I’ll figure it out and push a change to this branch.

[hasura-bot]

Review app for commit a0f7237 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-a0f72379

[ManUtopiK]

Just tested the last deploy: https://hge-ci-pull-3522.herokuapp.com/
I think it missing computed fields permissions management. It should be something like "Computed fields select permissions" after column select permissions.

[ManUtopiK]

Also, if there are two columns; first_name with public permission and last_name with private permission, could computed field full_name be public?

Edit:
I just tested with a POST query to /v1/query:

{
    "type" : "create_select_permission",
    "args" : {
        "table" : "author",
        "role" : "public",
        "permission" : {
            "columns" : ["first_name"],
            "computed_fields": ["full_name"],
            "filter": {}
        }
    }
}

And it works. full_name return first_name and last_name. It means that permission in computed field can override permission in column field. Developper should be careful with that.

[hasura-bot]

Review app for commit b7e6c86 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-b7e6c86a

[hasura-bot]

Review app for commit f1ab375 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-f1ab3751

[hasura-bot]

Review app for commit 0028190 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-0028190a

[rikinsk]

This PR is finally feature complete and ready for merge

@marionschleifer @wawhal @lexi-lambda Please add your reviews .

@lexi-lambda The empty server migration file is now replaced by one added in another PR.

[hasura-bot]

Review app https://hge-ci-pull-3522.herokuapp.com is deleted

[hasura-bot]

Review app for commit 1f544d9 deployed to Heroku: https://hge-ci-pull-3522.herokuapp.com
Docker image for server: hasura/graphql-engine:pull3522-1f544d93