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

[TS migration] Migrate AttachmentCarousel to typescript #36658

Merged

Conversation

SzymczakJ
Copy link
Contributor

@SzymczakJ SzymczakJ commented Feb 16, 2024

Details

Fixed Issues

$ #25152
PROPOSAL: N/A

Tests

  • Send few attachments in report and verify they show correctly, through clicking them and switching them. Check all attachment types: image, pdf, video.
  • Verify that in case of having eReceipt in report, the receipt is shown correctly when clicking on it
  • Verify that user profile photo is showing correctly.
  • Create distance money request and verify that distance receipt show correctly.

Offline tests

QA Steps

Same as tests

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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 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
      • 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 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(theme.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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label so the design team can review the changes.
  • 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.

Screenshots/Videos

Android: Native
android.mov
Android: mWeb Chrome
android.web.mov
iOS: Native
ios.mov
iOS: mWeb Safari
iosweb.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

Comment on lines -155 to -156
isSingleItem={items.length === 1}
index={index}
Copy link
Contributor

Choose a reason for hiding this comment

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

why those props were removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's no longer used by CarouselItem, probably smb forgot to remove this.

src/components/Attachments/AttachmentView/index.tsx Outdated Show resolved Hide resolved
@SzymczakJ SzymczakJ marked this pull request as ready for review March 13, 2024 12:02
@SzymczakJ SzymczakJ requested a review from a team as a code owner March 13, 2024 12:02
@melvin-bot melvin-bot bot requested review from s77rt and removed request for a team March 13, 2024 12:03
/** URL to full-sized attachment, SVG function, or numeric static image on native platforms */
source: AttachmentsPropTypes.attachmentSourcePropType.isRequired,
type AttachmentViewProps = AttachmentViewOnyxProps &
Omit<Attachment, 'isAuthTokenRequired'> & {
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of omitting isAuthTokenRequired from Attachment. Make that prop optional in Attachment

/** The id of the report action related to the attachment */
reportActionID: PropTypes.string,
/** Extra styles to pass to View wrapper */
containerStyles?: Array<StyleProp<ViewStyle>>;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
containerStyles?: Array<StyleProp<ViewStyle>>;
containerStyles?: StyleProp<ViewStyle>;

Comment on lines 69 to 70
/** The id of the transaction related to the attachment */
transactionID?: string;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/** The id of the transaction related to the attachment */
transactionID?: string;

Already defined in Attachment


isHovered?: boolean;

optionalVideoDuration?: number;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
optionalVideoDuration?: number;

Attachment has prop duration let's use it instead


/** Whether the video is currently being hovered over */
isHovered: PropTypes.bool,
isHovered?: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
isHovered?: boolean;

Pick from AttachmentViewProps


type AttachmentViewPdfProps = Pick<AttachmentViewProps, 'file' | 'onPress' | 'isUsedInCarousel' | 'isFocused' | 'onToggleKeyboard'> & {
encryptedSourceUrl: string;
onToggleKeyboard?: (shouldFadeOut: boolean) => void;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
onToggleKeyboard?: (shouldFadeOut: boolean) => void;

Already defined

@SzymczakJ SzymczakJ requested a review from s77rt March 20, 2024 11:40
@s77rt
Copy link
Contributor

s77rt commented Mar 20, 2024

@SzymczakJ We have a failing performance test. Can you please merge main see if that fixes it

@SzymczakJ
Copy link
Contributor Author

@s77rt had to merge it twice but it passed 😄

@s77rt
Copy link
Contributor

s77rt commented Mar 21, 2024

@SzymczakJ Thank you!

Copy link

melvin-bot bot commented Mar 21, 2024

We did not find an internal engineer to review this PR, trying to assign a random engineer to #25152 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot bot requested a review from puneetlath March 21, 2024 17:39
Copy link
Contributor

@puneetlath puneetlath left a comment

Choose a reason for hiding this comment

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

Just some minor comments/questions.

import type {FileObject} from '@components/AttachmentModal';
import type IconAsset from '@src/types/utils/IconAsset';

// This can be either a string, function, or number
Copy link
Contributor

Choose a reason for hiding this comment

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

This comment doesn't really add any value. The line below makes that clear. If we think this is an interesting or important point, it'd be good to add "why".

src/components/Attachments/types.ts Outdated Show resolved Hide resolved
src/components/Attachments/AttachmentCarousel/types.ts Outdated Show resolved Hide resolved
src/components/Attachments/AttachmentView/index.tsx Outdated Show resolved Hide resolved
@SzymczakJ SzymczakJ requested a review from puneetlath March 25, 2024 08:34
@SzymczakJ
Copy link
Contributor Author

@puneetlath fixed your comments!

@puneetlath puneetlath merged commit bcd4878 into Expensify:main Mar 25, 2024
16 checks passed
Copy link

melvin-bot bot commented Mar 25, 2024

@puneetlath looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@melvin-bot melvin-bot bot added the Emergency label Mar 25, 2024
@puneetlath
Copy link
Contributor

All the tests did pass.

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.

5 participants