Firestore: query_engine.test.ts: fix logic that checks configureCsi
#7501
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.
The unit tests in
query_engine.test.ts
are parameterized on aconfigureCsi
boolean variable. Some tests are if anif (configureCsi)
block, some are in anif (!configureCsi)
block, and others are in neither, and run for both values ofconfigureCsi
. However, the entire test suite was inside theif (!configureCsi)
block, nesting the checks forif (configureCsi)
which would unconditionally evaluate to false, causing those tests to never be run. This was likely a coding accident due to the subtle indenting difference.This PR fixes this by putting the
if (configureCsi)
,if (!configureCsi)
, and the other block at the same nesting level so that the appropriate tests are run for the appropriate values ofconfigureCsi
.Note to reviewers: Turn off whitespace when looking at the diff, since the vast majority of lines affected by this PR are whitespace-only changes due to indentation level changes.