chore: limit graphColorMapping to CLOUD #6641
Draft
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.
Part of #6307
@jeffreyssmith2nd traced this bug to this PR adding color persistence features (
graphColorMapping
) to UI visualizations. It was part of this epic.#5233 removed feature flag protection on that feature, resulting in it becoming part of the UI codebase for OSS and Cloud. It's causing serious visualization rendering issues in OSS (but not CLOUD, seemingly). To unblock the OSS team, which has the UI pinned to an older version to resolve this issue, we're going to proceed without the
graphColorMapping
feature in OSS, at least for now, so that OSS doesn't need to stay pinned to an outdated UI.Checklist
Authors and Reviewer(s), please verify the following: