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.
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
GH-1969 Plus In App Promo & GH-1970 Telemetry #509
GH-1969 Plus In App Promo & GH-1970 Telemetry #509
Changes from 1 commit
d7a2d6d95280ff887f445c14cf556301df3bedad1004a976031121c12b5497270c9fa156d07164f187afea8f83fe3140f5121cafb406fec5e6771a416ed0d1File filter
Jump to
Merge insights, plus, and premium PromoModal methods
This file was deleted.
Eden12345Apr 7, 2020
Contributor
Is this component not with the other modal content components because it is only used in the panel? Even if that's the case, I would opt for keeping them together in one
modal-contentdirectory inshared-components.benstrumeyerApr 7, 2020
Author
Contributor
The
PremiumPromoModalis the only one that's being used in the hub. But yeah it makes more sense just to bag them all together in there too since it might be an option at one point. Moved!Eden12345Apr 7, 2020
•
edited
Contributor
I'm still confused as to why this outer
<div />and<ExitButton />can't be moved out of each individual modal content component and into the parent<PromoModal />component. From what I can tell, the only difference between them is the main class name (which you can determine in<PromoModal />with theclassnameslibrary), and the<ExitButton />click handler (which you're already determining in<PromoModal />, but then pass down to the child components).benstrumeyerApr 7, 2020
•
edited
Author
Contributor
Moved the ExitButton out! Making a fragment inside each
PromoModalContentclass messed up the CSS so I couldn't abstract out the flex styles, but the Exit button is inside the PromoModal.jsx component nonetheless!