[UXE-6402] feat: implement banner visibility logic based on FORCE_REDIRECT_TO_CONSOLE flag #2181
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.
Pull Request
What is the new behavior introduced by this PR?
This pull request includes changes to the
src/stores/account.js
andsrc/views/Home/HomeView.vue
files. The main focus of these changes is to introduce a new feature flag and utilize it to control the visibility of a banner on the home view.Feature flag additions and usage:
src/stores/account.js
: Added a new feature flagFORCE_REDIRECT_TO_CONSOLE
to theflags
object and implemented a new getterisBannerVisible
to determine the visibility of a banner based on this flag. [1] [2]Home view modifications:
src/views/Home/HomeView.vue
: Updated the usage ofuseAccountStore
to include theisBannerVisible
getter and conditionally rendered theInlineMessage
component based on the value ofisBannerVisible
. [1] [2]Does this PR introduce breaking changes?
Does this PR introduce UI changes? Add a video or screenshots here.
NO
Does it have a link on Figma?
NO
Checklist
Make sure your pull request fits the checklist below (when applicable):
These changes were tested on the following browsers: