-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[$500] Tag - "Show more" button does not expand the list when clicked on #34761
Comments
Triggered auto assignment to @puneetlath ( |
Job added to Upwork: https://www.upwork.com/jobs/~014922c638cdf27d55 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
@greg-schroeder - #wave6-collect-submitters |
ProposalPlease re-state the problem that we are trying to solve in this issue."Show more" button does not trigger on press. What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?We need to manually call ListFooterComponent={renderFooterContent()} What alternative solutions did you explore? (Optional)NA ResultScreen.Recording.2024-01-19.at.03.39.56-compressed.mov |
ProposalPlease re-state the problem that we are trying to solve in this issue."Show more" button does not trigger on press. What is the root cause of that problem?we wrongly pass the footer content as a function, not components values here: That is why the OptionsList parses it as a function not react components: App/src/components/OptionsSelector/BaseOptionsSelector.js Lines 579 to 590 in 0ea199f
What changes do you think we should make in order to solve the problem?we need to change it to: renderFooterContent={
shouldShowShowMoreButton && (
<ShowMoreButton
containerStyle={{...this.props.themeStyles.mt2, ...this.props.themeStyles.mb5}}
currentCount={CONST.MAX_OPTIONS_SELECTOR_PAGE_LENGTH * this.state.paginationPage}
totalCount={this.state.allOptions.length}
onPress={this.incrementPage}
/>
)
} |
Not sure then how #31447 was working. |
This is a regression from #32464. They add a |
@abzokhattab's proposal LGTM. |
Sounds good to me. |
📣 @Ollyws 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @abzokhattab 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
This issue has not been updated in over 15 days. @puneetlath, @Ollyws, @abzokhattab eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Whoops, looks like the automation failed on this one and @abzokhattab and @Ollyws need to be paid. |
@abzokhattab was paid. @Ollyws you need to accept the offer: https://www.upwork.com/nx/wm/offer/28117886 |
Accepted, thanks! |
All paid. Thanks y'all! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.27-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
Action Performed:
Precondition: User is an employee of a Collect workspace that has 700 tags.
Expected Result:
The list will expand.
Actual Result:
Nothing happens when clicking on Show more. This issue also happens in contact selection list when the list is long enough.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6346915_1705605433972.20240119_012658.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: