-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data Model page busted if you visit a database that doesn't exist #14652
Labels
Administration/Table Metadata
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Type:Bug
Product defects
Milestone
Comments
camsaul
changed the title
Data Model page busted if there are no databases
Data Model page busted if you visit a database that doesn't exist
Feb 4, 2021
flamber
added
Administration/Table Metadata
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Type:UX
Type:Bug
Product defects
.Frontend
and removed
.Needs Triage
Type:Bug
Product defects
Type:UX
labels
Feb 4, 2021
Related to #11037 |
kulyk
added a commit
that referenced
this issue
Jun 22, 2021
* Add repro for #14652 * Fix blank screen when DB does not exist DataSelector assumes `schemas` is an array. But it's `undefined` if db does not exist * Fix data model page state when DB does not exist * Move prop-types to the top * Fix invalid database request
This was referenced Apr 21, 2023
This was referenced Jan 11, 2024
This was referenced Feb 5, 2024
Merged
Open
This was referenced Apr 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Administration/Table Metadata
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Type:Bug
Product defects
Probably an edge case, but we should make sure pages don't look insane if there isn't anything to display. It seems like it's not handling 404 (or other error) responses from the backend correctly.
Steps to repro
The text was updated successfully, but these errors were encountered: