Prices fetch from supportFrontend removed#1575
Merged
AnastasiiaBalenko merged 2 commits intomainfrom Mar 4, 2026
Merged
Conversation
AnastasiiaBalenko
added
the
maintenance
juabara
approved these changes
Mar 3, 2026
tomrf1
reviewed
Mar 3, 2026
| tickerSettings, | ||
| separateArticleCount: variant.separateArticleCount, | ||
| separateArticleCountSettings: variant.separateArticleCountSettings, | ||
| prices: productPrices.get(), |
Member
There was a problem hiding this comment.
we can also remove this field from the BannerProps model
AnastasiiaBalenko
deleted the
ab/prices-fetch-from-supportFrontend-removed
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Ticket link
What does this change?
This change removes the server-side prices fetch path from SDC, stops passing prices into banner API responses, deletes now-unused prices reloader/support-frontend utility code and its tests.
How has this change been tested?
Deployed to CODE, verified that all components are loaded without errors, no errors in logs.
How can we measure success?
Have we considered potential risks?
Images
Accessibility