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

Implement Search ListItems and table header #41347

Merged
merged 55 commits into from
May 3, 2024

Conversation

luacmartins
Copy link
Contributor

@luacmartins luacmartins commented Apr 30, 2024

Details

Introduces the TransactionListItem and SearchTableHeader to show list items in the search page

Fixed Issues

$ #39876
$ #39877

Tests

  1. Navigate to Profile > Troubleshoot > New Search Page
  2. Verify that you can see the table header and the transaction items.
  3. Verify that clicking on a transaction item opens the transaction thread in the RHP
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each 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

Screenshots/Videos

Android: Native
Android: mWeb Chrome

chrome

iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

web

MacOS: Desktop desktop

@luacmartins luacmartins self-assigned this Apr 30, 2024
@melvin-bot melvin-bot bot requested a review from amyevans May 2, 2024 22:22
Copy link

melvin-bot bot commented May 2, 2024

@amyevans Please 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]

@shawnborton
Copy link
Contributor

Not related to this PR but seeing some weirdness with some of the expense views in the RHP:
CleanShot 2024-05-02 at 20 33 17@2x

As in, I shouldn't see a Join button and the header styles are a bit different from a proper report/expense in the RHP:
CleanShot 2024-05-02 at 20 34 14@2x

@grgia
Copy link
Contributor

grgia commented May 3, 2024

@rayane-djouah are you able to build IOS without error

Copy link
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

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

changes LGTM, have we created issues for all the follow ups?

@grgia
Copy link
Contributor

grgia commented May 3, 2024

Coming from here should we sort by date descending to begin with? The transactions feel randomly organized right now

let columnWidth;
switch (columnName) {
case CONST.SEARCH_TABLE_COLUMNS.DATE:
columnWidth = getWidthStyle(variables.w44);
Copy link
Contributor

Choose a reason for hiding this comment

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

NAB these variables are typically named by their use, so like variables.dateColumnWidth

@rayane-djouah
Copy link
Contributor

@rayane-djouah are you able to build IOS without error

Yes, I'm able to. I merged main locally before testing.

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-05-03.at.11.18.10.mp4

@luacmartins
Copy link
Contributor Author

Gonna merge this one to get the feature out and then create a follow up to address the remaining issues. Thanks for the reviews everyone!

@luacmartins luacmartins merged commit da2cd90 into main May 3, 2024
17 checks passed
@luacmartins luacmartins deleted the cmartins-transactionListItem branch May 3, 2024 14:17
@OSBotify
Copy link
Contributor

OSBotify commented May 3, 2024

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

@shawnborton
Copy link
Contributor

Some more follow ups - the headers don't seem aligned to the content below:
CleanShot 2024-05-03 at 14 53 45@2x

cc @Expensify/design

@luacmartins
Copy link
Contributor Author

luacmartins commented May 3, 2024

@shawnborton I don't see that, which version are you using? Could you try this adhoc build? #40293 (comment)

@shawnborton
Copy link
Contributor

Yup I am using that adhoc build and noticed this.

@luacmartins
Copy link
Contributor Author

Weird, I'm on the same build and don't see that
Screenshot 2024-05-03 at 1 21 30 PM

@luacmartins
Copy link
Contributor Author

I do see some issues on iOS with the from/to fields though
simulator_screenshot_1BAE352D-1A58-4D44-B471-E36B7E7EF764

@shawnborton
Copy link
Contributor

It's probably because I have a mouse plugged in and the fixed header is above the scrollable area? And then the scroll bar pushes everything over?
CleanShot 2024-05-03 at 15 29 50@2x

@luacmartins luacmartins mentioned this pull request May 3, 2024
50 tasks
@luacmartins
Copy link
Contributor Author

Hmm I didn't test it with a mouse but I also just see the scrollbar below the header

Screen.Recording.2024-05-03.at.2.40.02.PM.mov

@luacmartins
Copy link
Contributor Author

@shawnborton do you see an additional right padding on the header? I see this padding, which makes the alignment correct
Screenshot 2024-05-03 at 2 41 46 PM

@shawnborton
Copy link
Contributor

Try testing it with a mouse though - I think the mouse creates that fixed scrollbar that is pushing the table to be over to the left a bit.

@luacmartins
Copy link
Contributor Author

Yea, adding the mouse shifted everything and that's also happening on other table views with scroll.
Screenshot 2024-05-06 at 12 20 41 PM
Screenshot 2024-05-06 at 12 20 58 PM

Gonna create a separate issue for this since multiple views are affected by it.

@shawnborton
Copy link
Contributor

Sounds good!

@OSBotify
Copy link
Contributor

OSBotify commented May 9, 2024

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.71-6 🚀

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants