hasura / hasura/graphql-engine
Console redirects to 404 url on metadata issue
Open
c/console
estimate/S
k/bug
support/needs-action
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Version Information
Server Version: confirmed on 2.0.9 through 2.1.0-beta.2
I had a situation where the metadata was inconsistent. When you go into the console, the app redirects you to the following url:
`https://[domain]/console/console/settings/metadata-status`
...which results in a 404; there are two `console` subpaths in the URL.
Contributor guide
Research direction
Reproduce the console flow with inconsistent metadata and inspect how the redirect URL is assembled. Trace the redirect from the console entry point to the metadata-status page. Done means the URL contains one /console path and the metadata issue no longer leads to a 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100