Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
metadata/actions.yaml and actions.graphql are not auto-updated after upgrading to v1.3.3
See original GitHub issueWith Hasura v1.3.2 when I created a new action in Hasura Console, both metadata/actions.yaml and metadata/actions.graphql were updated automatically.
Now in v1.3.3 I create a new action in Hasura Console, it is created successfully, listed and available via Hasura Console, but metadata/actions.* files are not updated any more - why?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Auto-update of apollo client cache after mutation not affecting ...
I have a mutation (UploadTransaction) returning certain list of certain object named Transaction. #import "TransactionFields.gql" mutation ...
Read more >Postgres: Update mutation | Hasura GraphQL Docs
You can update a single object in a table using the primary key. The output type is the nullable table object. The mutation...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The workaround works like a charm (for me). Thank you very much! BTW, I use graphql-engine.v1.3.2.
I think that was a typo, the right issue is https://github.com/hasura/graphql-engine/issues/6219