fix(database): Handle String errors in DatabaseModal #21709
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
At some point we stopped handling and displaying API errors coming as raw strings in the DatabaseModal. We are bringing that back, so for example, if someone tries to connect a BigQuery DB using credential JSON files with no roles in it, an error gets displayed vs no indication at all.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
After:
TESTING INSTRUCTIONS
Create a new Service Account on Google Console. Doesn’t grant any Role to it.
Download the Service Account key via jSON.
Access your Workspace.
Hover over the + on the top right corner, then navigate to Data > Connect database.
Select Google BigQuery.
Click on Choose File to upload the JSON.
Click on CONNECT.
ADDITIONAL INFORMATION