-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: [UIE-8163] - DBaaS V2 Landing Page platform fix #11030
Conversation
Coverage Report: β
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Over all LGTM! left feedback for using isFeatureEnabledV2
|
||
const createClusterButton = container.querySelector('button'); | ||
const headers = within(table).getAllByRole('columnheader'); | ||
expect(headers.some((header) => header.textContent === 'Plan')).toBe(true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use getByText
: Instead of manually iterating through the headers to check for the 'Plan' text,
example : expect(screen.getByText('Plan')).toBeInTheDocument();
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can resolve outside a hotfix
@@ -38,11 +38,31 @@ export const useIsDatabasesEnabled = () => { | |||
account.capabilities.includes('Managed Databases Beta') && | |||
flags.dbaasV2?.enabled; | |||
|
|||
const isV2ExistingBetaUser = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could use the isFeatureEnabledV2
hook here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can refactor outside of a hotfix
Description π
Bug Fix: Landing Page V2 issue for New Beta Users
Changes π
Adjust the UI to send the correct platform field based on the user's account
Target release date ποΈ
10/01/24
Preview π·
How to test π§ͺ
Prerequisites
Beta Flag must be enabled, and the user must have the "Managed Databases Beta" account capability.
Verification steps
(How to verify changes)
Go to the Landing Page.
The appropriate Landing Page is displayed based on the User's account type.
As an Author I have considered π€
Check all that apply
π Doing a self review
β Our contribution guidelines
π€ Splitting feature into small PRs
β Adding a changeset
π§ͺ Providing/Improving test coverage
π Removing all sensitive information from the code and PR description
π© Using a feature flag to protect the release
π£ Providing comprehensive reproduction steps
π Providing or updating our documentation
π Scheduling a pair reviewing session
π± Providing mobile support
βΏ Providing accessibility support