refactor(QueryContext): separate all processing concerns into QueryContextProcessor #17497
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.
Background
When we have worked on #16991 we wanted to test the new functionalities in concrete and accurate unittest.
All chartData flows and its components are too couple to superset so it is impossible to create unittests.
The flows are not testable and so many components do not meet the very important principle SRP and the code became so dirty
So I've started to refactor it (#17344 ) but many changes were added and it was hard to review so I decided to split those changes into small PRs so will be easier to follow
This is the twelvth PR in a sequence of PRs to meet these
PR description
To meet SRP and preparing QueryContext for decoule it from superset
All the processing task there were moved to QueryContextProcessor
*Note- in the next future PR the creation of QueryContextProcssor will be removed from there to the QueryContext clients
and the clients will call the processor and not the QueryContext itself, then the queryContext methods will be removed
Test plans
There is no logic added so new tests are not required
Previous PRs