
                    For automatic-api, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

Hi @srghma @toxsick relay makes assumptions about the GraphQL server as outlined here We haven't made any attempt to implement this spec yet At a quick glance 

graphql engine relay support

Hey folks Sorry for the radio silence on the thread from the Hasura team Add Hasura Support for Mac M1
The Hasura Docker container does not work on the Mac M1 Docker preview

graphql engine Support for Mac M1

@shahidhk .. my understanding of the current JWT role workflow is:

The token is decoded 

graphql engine Handling multiple roles on the graphql client (possibly in the same query)

@supriyanta @EmaSuriano @jasonmorganson @evcodes @Pomazan-Bogdan @ptrobert @eaverdeja @mnlbox We have released the react-admin data provider for Hasura 

graphql engine create hasura adapter for react-admin

Super excited to announce that we just released 4.4.0-alpha.0 which includes OSS subscriptions and live queries support To install use postgraphile@next 

postgraphile Adding subscriptions

I set up the superb forum_example tutorial and thanks to Graphiql autocomplete (which mostly worked) 

postgraphile document how to do a mutation

You can (and should) use an access token and it's not too difficult:

configure an API in your Auth0 dashboard 

graphql engine Review and verify guide on Auth0 JWT Integration

However In the documentation it says:

After a JSON Web Token has been verified and decoded 

postgraphile Where JWT token is read from and how to use it with GraphiQL?

@cakemountain there was a new version released which should fix the problem I'm assuming this issue is specific to the MacOS 11 beta- running the hasura cli downloaded from GitHub immediately exits with Killed: 9

graphql engine cli exits with "Killed: 9" (MacOS 11 aka Big Sur)

@marionschleifer Thank you for the prompt response :)

You can add the SQL (with insert statements) as a migration If I understand what you mentioned clear 

graphql engine managing seed or data-only migrations

To add to this it would be great if
hasura migrate create init --from-server
would also include the current enum states 

graphql engine Data in enum tables should be tracked in console-generated migrations

@divramod You can change your variables input to be the object type and it should be fine after that:

To get the exact type name there (test_insert_input) you can use the docs tab on the hasura graphiql console :)

graphql engine [Question] Insert multiple objects at once with variables

@willmitchell @romcok @Nomad-Go We have added support for stringified JSON in Hasura claims section with v1.0.0-alpha38 

graphql engine JWT nested scopes currently not supported on AWS Cognito / Lambda

@hughjfchen Could you please share the build details?
I have a scaleway Arm64 server and I could setup a CI build on it 

postgrest Docker image compatible with ARM: is that possible?

To answer myself---I found the following solution works:
PostgresQL setup:

GraphQL query: 

postgraphile Feature Request: Batch query support

I'm not sure how to feel about this On one hand OR is important but to support it you can no longer have each condition be a query parameter 

postgrest Why aren't "OR" conditions currently supported?

The issue does not lie in SQL - I was talking about allowing custom mutations to utilise the FooPatch GraphQL type - currently custom mutations can only use the FooInput GraphQL type directly