[$250] [HOLD for Payment 2024-09-10][Search v2.1] [App] Create In filter

[luacmartins]

Implement this section of the design doc for the In filter only!

cc @adamgrzybowski @Kicu @WojtekBoman @Guccio163

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021833294167898155328
• Upwork Job ID: 1833294167898155328
• Last Price Increase: 2024-09-09

[melvin-bot]

Triggered auto assignment to @RachCHopkins (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[RachCHopkins]

Already added to project.

[RachCHopkins]

@luacmartins do I need to do anything here? Sorry, I'm new to this team.

[luacmartins]

Not yet, you'll have to wait until we implement this and the issue is ready for payment.

[melvin-bot]

@luacmartins, @RachCHopkins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[RachCHopkins]

Changing to monthly in that case!

[luacmartins]

The issue is still daily. We're looking for someone from SWM to take this on

[melvin-bot]

@luacmartins, @RachCHopkins Whoops! This issue is 2 days overdue. Let's get this updated quick!

[luacmartins]

SWM will pick this up once the current wave of filter issues is done.

[luacmartins]

PR is merged, but we still need to address this issue in a follow up

[Guccio163]

Hi, after research it looks like the filters' wrapping (issue above) is a matter of Text component, not even Advanced Filters one - it is just visible here, because of several MenuItems one under another in a single place. I'll look into it, hopefully it won't turn out to be a big one 🤞
cc: @luacmartins

[luacmartins]

@Guccio163 If that's an issue with the text component itself, I'm inclined to create a separate issue for it outside the search project. Would you mind writing a problem statement for it so we can get this issue created while we focus on search functionality?

[Guccio163]

@luacmartins Right now I'm consulting with SWM's android developers; I suspect this is a matter of how the shortening is implemented on Android and that their dynamics don't allow developers to enforce ending always exactly on the end of the available space, rather end earlier to not cut words randomly (what IOS supports and in this situation is better for us because it makes Texts aligned better).

I'll get back to you with possible solutions as soon as I'll be sure of our situation, right now the only possible (sensible) solution is to extend Android Native Text component to provide shortening like we need it, but this seems to be a big piece of work.

[Guccio163]

@luacmartins @rayane-djouah I think I might have found quite an elegant solution to this problem, I attach iPhone, Android and web comparison below, let me know if a result like this fullfills your expectations:

[Guccio163]

Note: Our problem solving approach at Expensify is to focus on high value problems and avoid small optimizations with results that are difficult to measure. We also prefer to identify and solve problems at their root. Given that, please ensure all proposed jobs fix a specific problem in a measurable way with evidence so they are easy to evaluate. Here's an example of a good problem/solution:

Problem: The Text component in MenuItem shortens the text too early and inconsistently.

Solution: Change MenuItem Text component's flex prop to 1, to force using all provided space and thus end in more or less the same place (depending on the content). We can change this behaviour in the whole app or only when using MenuItem in SearchAdvancedFilters, where the inconsistency is visible the most.

If we want this fix to be implemented in whole app this is a small change, I already made draft pull request to show the difference; From what I've checked, it shouldn't cause any bugs to previous usages, but I'll ask for QA tests in the issue dedicated for this bug.

[luacmartins]

@Guccio163 nice! Thanks for investigating this. I'm inclined to fix it in the whole App. This might lead to bugs, it's a really simple PR and easy to revert if needed. Let's do it.

[Guccio163]

Great, I'm waiting for an issue to link PR with then 😄

[luacmartins]

@Guccio163 created here. I linked the issue to the PR already

[rayane-djouah]

Note

The production deploy automation failed: This should be on [HOLD for Payment 2024-09-10] according to #48438 production deploy checklist, confirmed in #47676 (comment)

Payment is due today!

cc @RachCHopkins

[RachCHopkins]

@luacmartins can I please confirm that this is a standard $250 via Upwork for @rayane-djouah? (@Guccio163 being from SWM)

[luacmartins]

Correct

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021833294167898155328

[melvin-bot]

Current assignee @rayane-djouah is eligible for the External assigner, not assigning anyone new.

[RachCHopkins]

I think I just sent you an offer @rayane-djouah but it did something a little strange - can you please confirm?

[RachCHopkins]

Oh, I see - it was because you were super duper fast.

[RachCHopkins]

Payment Summary:

Contributor+: @rayane-djouah paid $250 via Upwork

Upwork job here

[RachCHopkins]

Contributor has been paid, the contract has been completed, and the Upwork post has been closed.