Skip to content

[HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$250] Workspace switcher search bar is in the wrong place #40826

Description

@rlinoz

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:**v1.4.64-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
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:
Slack conversation:

Action Performed:

Break down in numbered steps

  1. Add enough workspaces so the search in the workspace switcher is visible(8+)
  2. Open the workspace switcher

Expected Result:

Describe what you think should've happened
The search bar should be below the workspaces title
image

Actual Result:

Describe what actually happened
Search bar is below Choose workspace

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f05cea763c8e597d
  • Upwork Job ID: 1782868524583206912
  • Last Price Increase: 2024-04-23
  • Automatic offers:
    • getusha | Reviewer | 0
    • Krishna2323 | Contributor | 0
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 23, 2024
  2. melvin-bot commented on Apr 23, 2024

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. Krishna2323 commented on Apr 23, 2024

    @Krishna2323
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Workspace switcher search bar is in the wrong place

    What is the root cause of that problem?

    We have included the everything section as a section of selection list.

    {
    title: translate('workspace.switcher.everythingSection'),
    shouldShow: true,
    indexOffset: 0,
    data: [
    {
    text: CONST.WORKSPACE_SWITCHER.NAME,
    policyID: '',
    icons: [{source: Expensicons.ExpensifyAppIcon, name: CONST.WORKSPACE_SWITCHER.NAME, type: CONST.ICON_TYPE_AVATAR}],
    brickRoadIndicator: getIndicatorTypeForPolicy(undefined),
    isSelected: activeWorkspaceID === undefined,
    keyForList: CONST.WORKSPACE_SWITCHER.NAME,
    },
    ],
    },

    What changes do you think we should make in order to solve the problem?

    We first need to remove the section from SelectionList sections and create the jsx for everything section.

    pseudo-code:

                <View style={[styles.mh4, styles.flexRow, styles.justifyContentBetween, styles.alignItemsCenter, styles.mb1]}>
                    <Text
                        style={styles.label}
                        color={theme.textSupporting}
                    >
                        {translate('workspace.switcher.everythingSection')}
                    </Text>
                </View>
                <View>
                    <UserListItem
                        item={{
                            text: CONST.WORKSPACE_SWITCHER.NAME,
                            policyID: '',
                            icons: [{source: Expensicons.ExpensifyAppIcon, name: CONST.WORKSPACE_SWITCHER.NAME, type: CONST.ICON_TYPE_AVATAR}],
                            brickRoadIndicator: getIndicatorTypeForPolicy(undefined),
                            isSelected: activeWorkspaceID === undefined,
                            keyForList: CONST.WORKSPACE_SWITCHER.NAME,
                        }}
                        isFocused={false}
                        isDisabled={false}
                        showTooltip={false}
                        canSelectMultiple={false}
                        onSelectRow={() =>
                            selectPolicy({
                                text: CONST.WORKSPACE_SWITCHER.NAME,
                                policyID: '',
                                icons: [{source: Expensicons.ExpensifyAppIcon, name: CONST.WORKSPACE_SWITCHER.NAME, type: CONST.ICON_TYPE_AVATAR}],
                                brickRoadIndicator: getIndicatorTypeForPolicy(undefined),
                                isSelected: activeWorkspaceID === undefined,
                                keyForList: CONST.WORKSPACE_SWITCHER.NAME,
                            })
                        }
                    />
                </View>

    This will be placed before the selection list. This is just pseudo-code, props are filled randomly. Minor styling changes can be discussed during PR phase.

    What alternative solutions did you explore? (Optional)

    remove_everything_Section.mp4
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 23, 2024
  5. melvin-bot commented on Apr 23, 2024

    @melvin-bot
  6. changed the title [-]Workspace switcher search bar is in the wrong place[/-] [+][$250] Workspace switcher search bar is in the wrong place[/+] on Apr 23, 2024
  7. melvin-bot commented on Apr 23, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

  8. gijoe0295 commented on Apr 23, 2024

    @gijoe0295
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Search bar is below Choose workspace

    What is the root cause of that problem?

    This is a feature request

    What changes do you think we should make in order to solve the problem?

    1. Pass the BaseSelectionList's current TextInput component (wrapped inside a memoized variable) as a children of section's CustomSectionHeader. Of course, we'll need to update the types accordingly:

    if (section.CustomSectionHeader) {
    return <section.CustomSectionHeader section={section} />;
    }

    <section.CustomSectionHeader
        section={section}
    >
        {textInput}
    </section.CustomSectionHeader>
    1. Inside WorkspacesSectionHeader, render that children with proper style. In WorkspaceSwitcherPage:
      • Disable shouldShowTopTextInput (new prop) to hide the current text input
      • Move headerMessage to WorkspacesSectionHeader (or we can wrap inside the above mentioned variable)
      • Use iconLeft to display the magnifier icon and modify textInputLabel to Find a workspace.

    What alternative solutions did you explore? (Optional)

    NA

  9. Krishna2323 commented on Apr 23, 2024

    @Krishna2323
    Contributor

    Proposal Updated

    • Added a note and result video
  10. gijoe0295 commented on Apr 23, 2024

    @gijoe0295
    Contributor

    Proposal updated to include detailed implementation.

  11. getusha commented on Apr 24, 2024

    @getusha
    Contributor

    @gijoe0295 i don't like the idea of modifying BaseSelectionList just for this since it's used multiple places.
    @Krishna2323 could you provide a more complete branch to test? there are some details you missed from the design.

  12. 42 remaining items

  13. mallenexpensify commented on Jun 24, 2024

    @mallenexpensify
    Contributor

    @getusha , the job was created as a milestone in Upwork so it's been auto-paid. The hire date was before your cutoff date too, can you please rescind your offer request for payment via NewDot?

    Contributor: @Krishna2323 paid $250 via Upwork
    Contributor+: @getusha paid $250 via Upwork

  14. JmillsExpensify commented on Jun 24, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @getusha

  15. getusha commented on Jun 24, 2024

    @getusha
    Contributor

    @getusha , the job was created as a milestone in Upwork so it's been auto-paid. The hire date was before your cutoff date too, can you please rescind your offer request for payment via NewDot?

    @mallenexpensify apologies for the delay, just refunded the amount on UW

    Screenshot 2024-06-24 at 9 53 32 at night

  16. JmillsExpensify commented on Jun 25, 2024

    @JmillsExpensify
    Contributor

    I think we're good here now.

  17. mallenexpensify commented on Jun 26, 2024

    @mallenexpensify
    Contributor

    The hire date was before your cutoff date too, can you please rescind your offer request for payment via NewDot?

    @getusha we need to pay via Upwork here because you were assigned here before 5/9, your eligible date. Can you please rescind your NewDot payment request and accept this new job I created? Thx
    https://www.upwork.com/jobs/~01d662b6ac617b4224

  18. getusha commented on Jun 27, 2024

    @getusha
    Contributor

    @getusha we need to pay via Upwork here because you were assigned here before 5/9, your eligible date. Can you please rescind your NewDot payment request and accept this new job I created? Thx

    @mallenexpensify is there a way to refund the ND payment?

  19. mallenexpensify commented on Jun 28, 2024

    @mallenexpensify
    Contributor

    If you've already been paid via NewDot for this, let's not complicate things with a refund. Both you and I are assigned to this issue, I'll comment there that payment is already made and link to here (assuming it's $250). Also.. let's consider this an edge case, it should not be used as a reference in the future :)

  20. mallenexpensify commented on Jun 28, 2024

    @mallenexpensify
    Contributor

    d'oh, looks like you haven't accepted the job in Upwork, can you plz @getusha ?
    https://www.upwork.com/jobs/~01d662b6ac617b4224

  21. getusha commented on Jun 28, 2024

    @getusha
    Contributor

    d'oh, looks like you haven't accepted the job in Upwork, can you plz @getusha ?

    Accepted. thank you!

  22. mallenexpensify commented on Jun 28, 2024

    @mallenexpensify
    Contributor

    Paid, thanks @getusha
    Payment confirmation is correct above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions