hasura / hasura/graphql-engine

On the console objects with same name across schemas are incorrectly visible

Open
#7,978 0 comments 0 reactions 0 assignees View on GitHub
c/console estimate/M k/bug support/needs-action
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: 2.0.1
CLI Version (for CLI related issue): v2.1.0-beta.3

### Environment
local setup

### What is the expected behaviour?

We have 2 schemas with the each with a view with the same name. So ideally we should have 2 views
schema1.view_name and schema2.view_name
On clicking on modify of schema2.view_name -> we should get the query of schema2.view_name

### Keywords

### What is the current behaviour?

We have 2 schemas with the each with a view with the same name. So ideally we should have 2 views
schema1.view_name and schema2.view_name
But when we 'Modify' the view in schema2, we still get the query for schema1.view_name and on clicking modify, the sql query is also for schema1.view_name.

### How to reproduce the issue?

1. Create view schema1.view_name
2. Create view schema2.view_name
3. Now click on schema2.view_name and click modify

### Screenshots or Screencast

### Please provide any traces or logs that could help here.

### Any possible solutions?

### Can you identify the location in the source code where the problem exists?

### If the bug is confirmed, would you be willing to submit a PR?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the console with two schemas containing views named view_name, then follow the Modify action for schema2.view_name. Done means the console shows both views distinctly and loads the query belonging to the selected schema2.view_name rather than schema1.view_name.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
databases, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.