BUGFIX: 'fields' property missing from queryConfig in DataExplorer #1947
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.
Connect #1576
The problem
It appears the queryConfig in the
DataExplorer
got into a state where thefields
key was missing.The Solution
Toughen up the happy path of query creation in the
FieldList
component andtoggleField
function in/queryTransitions
Repro Steps (Assuming you are using Chrome)
DataExporer
fields
key from localStorageNotes
Really we should be validating every qC that gets saved to localStorage and preventing bogus state from getting saved in the first place.