hasura / hasura/graphql-engine
Refreshing the browser does not work from certain screens
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Version Information
Server Version: 2.16.0 (And previous versions)
### Environment
Any
### What is the current behaviour?
In the OSS version, refreshing the browser from certain screens shows the error "resource does not exist". In the Cloud version, refreshing the same screens redirects to /projects screen.
### What is the expected behaviour?
Refresh should work just like in any other screen.
### How to reproduce the issue?
Here are some scenarios in which this happens. Note that the same issue may exist in other scenarios as well.
Scenario 1
1. Create an cron trigger.
2. Click refresh on the browser.
Scenario 2
1. Navigate to Settings -> Allow List.
2. Click refresh on the browser.
### Screenshots or Screencast
Here is a screenshot of the error when refreshing from allow list screen in the OSS version -

### Any possible solutions/workarounds you're aware of?
The issue happens because the URL set in the browser is missing the /console prefix. Adding that again will make it work.
### Keywords
browser refresh
Contributor guide
Research direction
Reproduce the issue from a cron trigger and from Settings → Allow List, then inspect the browser URL when refreshing those screens. Done means refresh remains on the current screen and no longer produces “resource does not exist” in OSS or redirects to /projects in Cloud, without manually adding the /console prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100