Skip to content
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 styles for MoneyRequestHeader #18467

Merged
merged 4 commits into from
May 5, 2023
Merged

Fix styles for MoneyRequestHeader #18467

merged 4 commits into from
May 5, 2023

Conversation

yuwenmemon
Copy link
Contributor

@yuwenmemon yuwenmemon commented May 5, 2023

@luacmartins please review
cc @grgia @parasharrajat

?w=1 review reccomended

Details

After reverting the styles back to what they were originally in this PR: #18465 I went back to the drawing board to see how we could get the header to show properly for when we're using an AvatarWithDisplayName

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/270587

Tests

(Internal, dev)
Apply the following diff to your local code:

diff --git a/src/components/ReportActionItem/IOUAction.js b/src/components/ReportActionItem/IOUAction.js
index a7fe3f1710..6835776a87 100644
--- a/src/components/ReportActionItem/IOUAction.js
+++ b/src/components/ReportActionItem/IOUAction.js
@@ -67,7 +67,7 @@ const defaultProps = {
 
 const IOUAction = (props) => {
     const launchDetailsModal = () => {
-        Navigation.navigate(ROUTES.getIouDetailsRoute(props.chatReportID, props.action.originalMessage.IOUReportID));
+        Navigation.navigate(ROUTES.getReportRoute(props.action.originalMessage.IOUReportID));
     };
 
     const shouldShowIOUPreview = (
diff --git a/src/pages/home/ReportScreen.js b/src/pages/home/ReportScreen.js
index 6d573fe567..e32e41bc53 100644
--- a/src/pages/home/ReportScreen.js
+++ b/src/pages/home/ReportScreen.js
@@ -40,6 +40,7 @@ import getIsReportFullyVisible from '../../libs/getIsReportFullyVisible';
 import EmojiPicker from '../../components/EmojiPicker/EmojiPicker';
 import * as EmojiPickerAction from '../../libs/actions/EmojiPickerAction';
 import TaskHeaderView from './TaskHeaderView';
+import MoneyRequestHeader from '../../components/MoneyRequestHeader';
 
 const propTypes = {
     /** Navigation route context info provided by react navigation */
@@ -243,6 +244,17 @@ class ReportScreen extends React.Component {
         // (which is shown, until all the actual views of the ReportScreen have been rendered)
         const shouldAnimate = !shouldFreeze;
 
+        const moneyRequestHeader = this.props.report.type === 'iou' && this.props.report.reportID === '5571340985182399'
+            ? <MoneyRequestHeader report={this.props.report} policies={this.props.policies} personalDetails={this.props.personalDetails} />
+            : (
+                <HeaderView
+                    reportID={reportID}
+                    onNavigationMenuButtonClicked={() => Navigation.navigate(ROUTES.HOME)}
+                    personalDetails={this.props.personalDetails}
+                    report={this.props.report}
+                />
+            );
+
         return (
             <ScreenWrapper
                 style={screenWrapperStyle}
@@ -275,12 +287,7 @@ class ReportScreen extends React.Component {
                                     errors={addWorkspaceRoomOrChatErrors}
                                     shouldShowErrorMessages={false}
                                 >
-                                    <HeaderView
-                                        reportID={reportID}
-                                        onNavigationMenuButtonClicked={() => Navigation.navigate(ROUTES.HOME)}
-                                        personalDetails={this.props.personalDetails}
-                                        report={this.props.report}
-                                    />
+                                    {moneyRequestHeader}
                                 </OfflineWithFeedback>
                                 {Boolean(this.props.accountManagerReportID) && ReportUtils.isConciergeChatReport(this.props.report) && this.state.isBannerVisible && (
                                     <Banner

Replace the reportID in this line:

const moneyRequestHeader = this.props.report.type === 'iou' && this.props.report.reportID === '5571340985182399'

... with the reportID of an IOU report you have locally.

  1. Click the IOU
  2. See that you are taken to a blank component that renders the MoneyRequestHeader:
  3. Make sure everything at the top header is aligned:
    Screenshot 2023-05-04 at 10 39 33 PM

Screenshot 2023-05-04 at 10 39 43 PM


  1. Go to Settings -> Preferences, make sure the header is aligned
    Screenshot 2023-05-04 at 10 40 34 PM

Screenshot 2023-05-04 at 10 40 46 PM

  1. Load an attachment, make sure the attachment preview header is aligned:

Screenshot 2023-05-04 at 10 41 25 PM

Offline tests

  • N/A

QA Steps

  • None, this component cannot be accessed in the App just yet without modifying the code directly.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web Screenshot 2023-05-04 at 10 46 01 PM Screenshot 2023-05-04 at 10 46 05 PM Screenshot 2023-05-04 at 10 46 16 PM
Mobile Web - Chrome

Screenshot 2023-05-04 at 10 46 44 PM
Screenshot 2023-05-04 at 10 46 53 PM

Mobile Web - Safari

Screenshot 2023-05-04 at 10 47 36 PM
Screenshot 2023-05-04 at 10 47 42 PM

Desktop Screenshot 2023-05-04 at 10 50 29 PM Screenshot 2023-05-04 at 10 50 35 PM
iOS

Screenshot 2023-05-04 at 10 50 58 PM
Screenshot 2023-05-04 at 10 51 09 PM

Android

Screenshot 2023-05-04 at 10 59 37 PM
Screenshot 2023-05-04 at 10 59 50 PM

@yuwenmemon yuwenmemon requested a review from luacmartins May 5, 2023 06:00
@yuwenmemon yuwenmemon self-assigned this May 5, 2023
@yuwenmemon yuwenmemon requested a review from a team as a code owner May 5, 2023 06:00
@melvin-bot melvin-bot bot requested review from Beamanator and rushatgabhane and removed request for a team May 5, 2023 06:00
@melvin-bot
Copy link

melvin-bot bot commented May 5, 2023

@rushatgabhane @Beamanator One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@rushatgabhane
Copy link
Member

@yuwenmemon should I review this?

or @parasharrajat

luacmartins
luacmartins previously approved these changes May 5, 2023
Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@parasharrajat
Copy link
Member

parasharrajat commented May 5, 2023

No worries @rushatgabhane . I can do that now. it is a follow-up PR.

@luacmartins
Copy link
Contributor

@rushatgabhane @parasharrajat coming from this post, this is an EC3 issue so whoever can review first should do it.

@luacmartins
Copy link
Contributor

seems like @parasharrajat is on it now

@parasharrajat
Copy link
Member

parasharrajat commented May 5, 2023

The corner icon looks a little off although it has the correct padding as other icons. Should reduce the gap for it?
image

@parasharrajat
Copy link
Member

I am suggesting a few style change that looks better to me. Sorry, I could do that on the original PR because I was trying to figure out the testing.

Here is the diff of suggested changes. IMO, the flex1 should be applied to AvatarWithDisplayName container and no wrapper should be applied to HeaderWithcloseButton. This will keepHeaderWithcloseButton more flexible for future.

diff --git a/src/components/AvatarWithDisplayName.js b/src/components/AvatarWithDisplayName.js
index dfee2ca605..cb56b27b48 100644
--- a/src/components/AvatarWithDisplayName.js
+++ b/src/components/AvatarWithDisplayName.js
@@ -51,59 +51,57 @@ const AvatarWithDisplayName = (props) => {
     const ownerPersonalDetails = OptionsListUtils.getPersonalDetailsForLogins([props.report.ownerEmail], props.personalDetails);
     const displayNamesWithTooltips = ReportUtils.getDisplayNamesWithTooltips(ownerPersonalDetails, false);
     return (
-        <View>
-            <View style={[styles.appContentHeaderTitle]}>
-                {Boolean(props.report && title) && (
-                    <View
+        <View style={[styles.appContentHeaderTitle, styles.flex1]}>
+            {Boolean(props.report && title) && (
+            <View
+                style={[
+                    styles.flexRow,
+                    styles.alignItemsCenter,
+                    styles.justifyContentBetween,
+                ]}
+            >
+                {isExpenseReport ? (
+                    <SubscriptAvatar
+                        mainAvatar={icons[0]}
+                        secondaryAvatar={icons[1]}
+                        mainTooltip={props.report.ownerEmail}
+                        secondaryTooltip={subtitle}
+                        size={props.size}
+                    />
+                ) : (
+                    <Avatar
+                        size={props.size}
+                        source={icons[0].source}
+                        type={icons[0].type}
+                        name={icons[0].name}
+                        containerStyles={props.size === CONST.AVATAR_SIZE.SMALL ? styles.emptyAvatarSmall : styles.emptyAvatar}
+                    />
+                )}
+                <View style={[styles.flex1, styles.flexColumn, styles.ml3]}>
+                    <DisplayNames
+                        fullTitle={title}
+                        displayNamesWithTooltips={displayNamesWithTooltips}
+                        tooltipEnabled
+                        numberOfLines={1}
+                        textStyles={[styles.headerText, styles.pre]}
+                        shouldUseFullTitle={isExpenseReport}
+                    />
+                    {!_.isEmpty(subtitle) && (
+                    <Text
                         style={[
-                            styles.flexRow,
-                            styles.alignItemsCenter,
-                            styles.justifyContentBetween,
+                            styles.sidebarLinkText,
+                            styles.optionAlternateText,
+                            styles.textLabelSupporting,
+                            styles.pre,
                         ]}
+                        numberOfLines={1}
                     >
-                        {isExpenseReport ? (
-                            <SubscriptAvatar
-                                mainAvatar={icons[0]}
-                                secondaryAvatar={icons[1]}
-                                mainTooltip={props.report.ownerEmail}
-                                secondaryTooltip={subtitle}
-                                size={props.size}
-                            />
-                        ) : (
-                            <Avatar
-                                size={props.size}
-                                source={icons[0].source}
-                                type={icons[0].type}
-                                name={icons[0].name}
-                                containerStyles={props.size === CONST.AVATAR_SIZE.SMALL ? styles.emptyAvatarSmall : styles.emptyAvatar}
-                            />
-                        )}
-                        <View style={[styles.flex1, styles.flexColumn, styles.ml3]}>
-                            <DisplayNames
-                                fullTitle={title}
-                                displayNamesWithTooltips={displayNamesWithTooltips}
-                                tooltipEnabled
-                                numberOfLines={1}
-                                textStyles={[styles.headerText, styles.pre]}
-                                shouldUseFullTitle={isExpenseReport}
-                            />
-                            {!_.isEmpty(subtitle) && (
-                                <Text
-                                    style={[
-                                        styles.sidebarLinkText,
-                                        styles.optionAlternateText,
-                                        styles.textLabelSupporting,
-                                        styles.pre,
-                                    ]}
-                                    numberOfLines={1}
-                                >
-                                    {subtitle}
-                                </Text>
-                            )}
-                        </View>
-                    </View>
-                )}
+                        {subtitle}
+                    </Text>
+                    )}
+                </View>
             </View>
+            )}
         </View>
     );
 };
diff --git a/src/components/HeaderWithCloseButton.js b/src/components/HeaderWithCloseButton.js
index 6b012a3ee0..0ec4726558 100755
--- a/src/components/HeaderWithCloseButton.js
+++ b/src/components/HeaderWithCloseButton.js
@@ -165,30 +165,28 @@ class HeaderWithCloseButton extends Component {
                     styles.overflowHidden,
                 ]}
                 >
-                    <View style={[styles.flexRow, this.props.shouldShowAvatarWithDisplay && styles.flex1]}>
-                        {this.props.shouldShowBackButton && (
-                            <Tooltip text={this.props.translate('common.back')}>
-                                <Pressable
-                                    onPress={() => {
-                                        if (this.props.isKeyboardShown) {
-                                            Keyboard.dismiss();
-                                        }
-                                        this.props.onBackButtonPress();
-                                    }}
-                                    style={[styles.touchableButtonImage]}
-                                >
-                                    <Icon src={Expensicons.BackArrow} />
-                                </Pressable>
-                            </Tooltip>
-                        )}
-                        {this.props.shouldShowAvatarWithDisplay && (
-                            <AvatarWithDisplayName
-                                report={this.props.report}
-                                policies={this.props.policies}
-                                personalDetails={this.props.personalDetails}
-                            />
-                        )}
-                    </View>
+                    {this.props.shouldShowBackButton && (
+                    <Tooltip text={this.props.translate('common.back')}>
+                        <Pressable
+                            onPress={() => {
+                                if (this.props.isKeyboardShown) {
+                                    Keyboard.dismiss();
+                                }
+                                this.props.onBackButtonPress();
+                            }}
+                            style={[styles.touchableButtonImage]}
+                        >
+                            <Icon src={Expensicons.BackArrow} />
+                        </Pressable>
+                    </Tooltip>
+                    )}
+                    {this.props.shouldShowAvatarWithDisplay && (
+                    <AvatarWithDisplayName
+                        report={this.props.report}
+                        policies={this.props.policies}
+                        personalDetails={this.props.personalDetails}
+                    />
+                    )}
                     {!this.props.shouldShowAvatarWithDisplay && (
                         <Header
                             title={this.props.title}

@parasharrajat
Copy link
Member

More changes, we should remove the containerStyles from the HeaderWithCloseButton in MoneyRequestHeader.

diff --git a/src/components/MoneyRequestHeader.js b/src/components/MoneyRequestHeader.js
index 728ff0a227..df09048c6a 100644
--- a/src/components/MoneyRequestHeader.js
+++ b/src/components/MoneyRequestHeader.js
@@ -73,7 +73,6 @@ const MoneyRequestHeader = (props) => {
                 report={props.report}
                 policies={props.policies}
                 personalDetails={props.personalDetails}
-                containerStyles={[styles.pt5, styles.pb3, styles.pr1]}
                 shouldShowCloseButton={false}
                 shouldShowBackButton={props.isSmallScreenWidth}
                 onBackButtonPress={() => Navigation.navigate(ROUTES.HOME)}

@parasharrajat
Copy link
Member

Doing the above changes will keep the design as they are bug fixes for a few alignment issues.

@yuwenmemon
Copy link
Contributor Author

Thanks @parasharrajat! Updated!

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mweb
image

Chrome

image

@mountiny
Copy link
Contributor

mountiny commented May 5, 2023

Tests good @parasharrajat let us know if you wont be able to get to this review

@mountiny
Copy link
Contributor

mountiny commented May 5, 2023

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified tests pass on all platforms & I tested again on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

image

Mobile Web - Chrome image
Mobile Web - Safari

image

Desktop

same as web

iOS image
Android image

@mountiny
Copy link
Contributor

mountiny commented May 5, 2023

Atually did the testing and we are good to go

@mountiny mountiny merged commit 86dc736 into main May 5, 2023
@mountiny mountiny deleted the yuwen-mrmStyles branch May 5, 2023 23:52
@OSBotify
Copy link
Contributor

OSBotify commented May 5, 2023

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@parasharrajat
Copy link
Member

Thanks for taking care of this. I was asleep but I already tested. If suggestion were applied as it is then everything will be good.

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@parasharrajat
Copy link
Member

parasharrajat commented May 8, 2023

Can someone create a job for C+ payout for this PR and #18148? cc: @mountiny

There should be a label to do that. Not sure which one.

@luacmartins
Copy link
Contributor

The issue should have been created automatically, since the PR points to an E/E internal issue. Not sure why it wasn't created.

@luacmartins
Copy link
Contributor

Created payment issue here

@yuwenmemon yuwenmemon restored the yuwen-mrmStyles branch May 8, 2023 17:28
@yuwenmemon yuwenmemon deleted the yuwen-mrmStyles branch May 8, 2023 17:34
@mountiny
Copy link
Contributor

mountiny commented May 8, 2023

Its created only when C+ approved the PR and Rajat could not do that after it was merged.

@OSBotify
Copy link
Contributor

OSBotify commented May 9, 2023

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.12-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 failure ❌
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented May 9, 2023

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.12-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented May 9, 2023

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.12-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants