Refactoring ahead of tg caching fix - pt 1 #418
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.
What type of PR is this?
cleanup
Which issue does this PR fix:
This PR includes basic readability improvements, including refactoring of large methods, more descriptive naming for variables and functions, and consistency in imports. There should be NO FUNCTIONAL CHANGES in this PR.
One thing I would like to get feedback on are the contents of the Developer Cheat Sheet.
What does this PR do / Why do we need it:
This is part of a larger refactor which will ultimately remove the lattice data store, specifically for target groups.
Testing done on this change:
Automation added to e2e:
No changes
Will this PR introduce any new dependencies?:
No
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
n/a
Does this PR introduce any user-facing change?:
No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.