-
Notifications
You must be signed in to change notification settings - Fork 314
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(content-sidebar): remove dependency on isSignRemoveInterstitialEnabled #3734
base: master
Are you sure you want to change the base?
fix(content-sidebar): remove dependency on isSignRemoveInterstitialEnabled #3734
Conversation
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.
One question and one small followup, if possible (can be another PR)
aea92d0
to
1020007
Compare
1020007
to
bdba5eb
Compare
bdba5eb
to
3b5d387
Compare
3b5d387
to
a982541
Compare
f4855fe
to
8fd8f2e
Compare
8fd8f2e
to
ba55f34
Compare
b0d2d93
to
8a40819
Compare
cbf2ac3
to
f54b7ad
Compare
}: Props) => { | ||
const { enabled: hasBoxSign } = useFeatureConfig('boxSign'); | ||
const { enabled: hasBoxSign } = signSideBarProps || {}; |
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.
is there a permission via the user that enables this feature too ?
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.
Yes, there is a user permission controlled by the admin that enables/disables signing. This is reflected in the enabled
property sent by EUA
f54b7ad
to
8aed68f
Compare
8aed68f
to
60f54fc
Compare
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.
approved but this feature has remain undocumented, normally all props at the root level is usable by 3rd customers sine this feature is only enabled by a flag and additional unknown permissions internally, we cant guarantee the 3rd party customers will be able to use it.
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.
some minor things I think worth cleaning up
6e7c952
to
bf63860
Compare
7d214a8
to
6ba3efd
Compare
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.
lgtm
@@ -25,11 +25,11 @@ export type Props = PlainButtonProps & { | |||
|
|||
export const PlaceholderTooltip = ({ children }: { children: React.ReactNode }) => children; | |||
|
|||
export function SidebarNavSignButton({ blockedReason, intl, status, targetingApi, ...rest }: Props) { |
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 status
be removed from prop type?
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.
yes, is safe to remove it. Updated
6ba3efd
to
f3071a5
Compare
The isSignRemoveInterstitialEnabled feature flag was recently cleaned up on the application side, causing a production defect due to a dependency in this components. This PR removes the dependency in BUIE components to align with the application.
Also uses sign config in the primary props instead of feature props