Only list tables in DB test if API returns them (which it doesn't) #8681
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.
…ever will)
CATEGORY
Choose one
SUMMARY
I noticed that when you use the button to test a DB connection, the API just responds with "OK" and not a list of tables. That may be an issue worth exploring, or maybe it was changed for a good reason. In any case, there was some Javascript that was bugging out in trying to process/display a list of tables from that "OK" so I made this display logic conditional, such that it will only run if an array of tables is indeed returned. I doubt that will ever happen, but at least this PR kills the console error in any case.
REVIEWERS
@mistercrunch