hasura / hasura/graphql-engine
Api limits: warn when user setting limits greater than platform limit
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Is your proposal related to a problem?
Hasura cloud recently introduced platform limits with a default timeout of 60s for most operations.
This can be confusing to users who may encounter the related error message, head to the api limits console tab and set a timeout greater than that, and not see the desired effect.
### Describe the solution you'd like
Users should either get a warning or be prevented entirely from setting api limits greater than the platform limits.
Contributor guide
Research direction
Start by locating the API limits console and the handling of platform limits. Verify how values above the platform timeout are currently accepted, then add a warning or prevention and confirm that exceeding the platform limit no longer appears effective.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100