hasura / hasura/graphql-engine
Hasura should emit codegen files
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Hello all,
Today I find Hasura action's highly impratical in term of integration with TypeScript.
The codegen tab is a good idea, but why stop there and make people copy/paste code? It would be way better to emit at least the hasuraCustomTypes.ts file so we can directly import it and it becomes a reliable artefact. The console could just reflect changes to this file anytime we use the UI the modify the actions, and without touching anything else we would know that we broke our handler.
Contributor guide
Research direction
Start by tracing the Actions codegen tab and the Hasura console flow that modifies actions. Determine where the generated hasuraCustomTypes.ts content is assembled and how console changes are persisted. Done means the console emits that file as a reliable artefact and keeps it updated when actions are changed through the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100