[HOLD for payment 2024-07-17][$500] Move "Troubleshoot" out of About and into Settings as its own nav item #38594

shawnborton · 2024-03-19T14:36:59Z

We want to take the Troubleshoot page:

And move it into the Settings navigation as it's own nav item, right above the Sign Out option at the bottom. When doing this, the Troubleshoot UI should look like the About page, where we use the card style and a nice header with an illustration + h2:

cc @TMisiukiewicz since I think you originally implemented this? This would just be a follow up to that.

cc @muttmuure @Expensify/design

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01928d4373947e3fe3
Upwork Job ID: 1770771675763638272
Last Price Increase: 2024-03-28
Automatic offers:

alitoshmatov | Reviewer | 0
tienifr | Contributor | 0

Issue Owner

Current Issue Owner: @muttmuure

melvin-bot · 2024-03-19T14:37:10Z

Triggered auto assignment to @muttmuure (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

melvin-bot · 2024-03-19T14:37:12Z

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

allgandalf · 2024-03-19T14:39:34Z

Can this be opened to external contributors as this is a relatively simple feature to implement :)

ghost · 2024-03-19T16:20:41Z

Proposal

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

Move "Troubleshoot" out of About and into Settings as its own nav item

What is the root cause of that problem?

This is the a New Feature

The Troubleshoot is inside About Page i.e. here :

App/src/pages/settings/AboutPage/AboutPage.tsx

Lines 90 to 94 in 71e3aa4

    
           { 
        
               translationKey: 'initialSettingsPage.aboutPage.troubleshoot', 
        
               icon: Expensicons.Lightbulb, 
        
               action: waitForNavigate(() => Navigation.navigate(ROUTES.SETTINGS_TROUBLESHOOT)), 
        
           },

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

We need to move it into InitialPage, just above Signout button here :

App/src/pages/settings/InitialSettingsPage.tsx

Lines 250 to 256 in 71e3aa4

    
           { 
        
               translationKey: signOutTranslationKey, 
        
               icon: Expensicons.Exit, 
        
               action: () => { 
        
                   signOut(false); 
        
               }, 
        
           },

Also, we need to modify the Troubleshoot completely to look like About Us Page
https://github.com/Expensify/App/blob/860cca67cd3ee3309af766dee54b97a14df19556/src/pages/settings/AboutPage/TroubleshootPage.tsx

What alternative solutions did you explore? (Optional)

N/A

Result :

ADDED TEST BRANCH - https://github.com/godofoutcasts94/App/tree/moving-troubleshoot-page

Need Illustration to be added.

ghost · 2024-03-19T16:23:37Z

Updated Proposal

ghost · 2024-03-19T21:13:47Z

Upated Proposal, will add updated screenshot in sometime

muttmuure · 2024-03-21T11:17:14Z

I think we should actually make this an External issue, since Tomasz is working on a higher value performance project

melvin-bot · 2024-03-21T11:17:23Z

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

melvin-bot · 2024-03-21T11:17:28Z

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

ghost · 2024-03-21T11:18:49Z

Hey @muttmuure, I have already posted a proposal and I am already working. Should I complete it and post a test branch in the proposal ?

shubham1206agra · 2024-03-21T11:37:54Z

Proposal

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

Move "Troubleshoot" out of About and into Settings as its own nav item

What is the root cause of that problem?

New Feature request.

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

We need to move the Troubleshoot from inside the About Page

App/src/pages/settings/AboutPage/AboutPage.tsx

Lines 90 to 94 in 71e3aa4

    
           { 
        
               translationKey: 'initialSettingsPage.aboutPage.troubleshoot', 
        
               icon: Expensicons.Lightbulb, 
        
               action: waitForNavigate(() => Navigation.navigate(ROUTES.SETTINGS_TROUBLESHOOT)), 
        
           },

To InitialPage, just above the Signout button

App/src/pages/settings/InitialSettingsPage.tsx

Lines 250 to 256 in 71e3aa4

    
           { 
        
               translationKey: signOutTranslationKey, 
        
               icon: Expensicons.Exit, 
        
               action: () => { 
        
                   signOut(false); 
        
               }, 
        
           },

We also need to update the CENTRAL_PANE_TO_RHP_MAPPING to

[SCREENS.SETTINGS.ABOUT]: [SCREENS.SETTINGS.APP_DOWNLOAD_LINKS],
[SCREENS.SETTINGS.TROUBLESHOOT]: [SCREENS.SETTINGS.CONSOLE],

We must also update the CentralPaneNavigatorParamList to add SCREENS.SETTINGS.TROUBLESHOOT.

We also need to update TAB_TO_CENTRAL_PANE_MAPPING to add SCREENS.SETTINGS.TROUBLESHOOT.

The Troubleshoot Page design would be similar to AboutPage.

And minor changes to linkingConfig.

Test branch : https://github.com/shubham1206agra/App/tree/test-troubleshoot-pag

Screenshot

What alternative solutions did you explore? (Optional)

N/A

ShridharGoel · 2024-03-21T11:42:30Z

Proposal

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

What is the root cause of that problem?

New feature.

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

Troubleshoot is currently set as RHP.

In linkingConfig/config.ts

Add this under NAVIGATORS.CENTRAL_PANE_NAVIGATOR

[SCREENS.SETTINGS.TROUBLESHOOT]: {
    path: ROUTES.SETTINGS_TROUBLESHOOT,
    exact: true,
},

And remove it from NAVIGATORS.RIGHT_MODAL_NAVIGATOR.

Add this in BaseCentralPaneNavigator.tsx inside settingsScreen

    [SCREENS.SETTINGS.TROUBLESHOOT]: () => require('../../../../../pages/settings/AboutPage/TroubleshootPage').default as React.ComponentType,

App/src/libs/Navigation/AppNavigator/Navigators/CentralPaneNavigator/BaseCentralPaneNavigator.tsx

Lines 16 to 23 in 8206580

    
           const settingsScreens = { 
        
               [SCREENS.SETTINGS.WORKSPACES]: () => require('../../../../../pages/workspace/WorkspacesListPage').default as React.ComponentType, 
        
               [SCREENS.SETTINGS.PREFERENCES.ROOT]: () => require('../../../../../pages/settings/Preferences/PreferencesPage').default as React.ComponentType, 
        
               [SCREENS.SETTINGS.SECURITY]: () => require('../../../../../pages/settings/Security/SecuritySettingsPage').default as React.ComponentType, 
        
               [SCREENS.SETTINGS.PROFILE.ROOT]: () => require('../../../../../pages/settings/Profile/ProfilePage').default as React.ComponentType, 
        
               [SCREENS.SETTINGS.WALLET.ROOT]: () => require('../../../../../pages/settings/Wallet/WalletPage').default as React.ComponentType, 
        
               [SCREENS.SETTINGS.ABOUT]: () => require('../../../../../pages/settings/AboutPage/AboutPage').default as React.ComponentType, 
        
           } satisfies Screens;

Remove SCREENS.SETTINGS.TROUBLESHOOT from [SCREENS.SETTINGS.ABOUT] in CENTRAL_PANE_TO_RHP_MAPPING.

Add SCREENS.SETTINGS.TROUBLESHOOT in TAB_TO_CENTRAL_PANE_MAPPING

Add [SCREENS.SETTINGS.TROUBLESHOOT]: undefined; in CentralPaneNavigatorParamList.

Add below in InitialSettingsPage items list

{
    translationKey: 'initialSettingsPage.aboutPage.troubleshoot',
    icon: Expensicons.Lightbulb,
    routeName: ROUTES.SETTINGS_TROUBLESHOOT,
},

And remove it the troubleshoot option from About page.

Example code for the UI (can be polished)

<ScreenWrapper
shouldEnablePickerAvoiding={false}
shouldShowOfflineIndicatorInWideScreen
testID={TroubleshootPage.displayName}
>
<HeaderWithBackButton
    title={translate('initialSettingsPage.aboutPage.troubleshoot')}
    shouldShowBackButton={isSmallScreenWidth}
    onBackButtonPress={() => Navigation.goBack()}
    icon={Expensicons.Lightbulb2}
/>
<ScrollView contentContainerStyle={styles.pt3}>
    <View style={[styles.flex1, isSmallScreenWidth ? styles.workspaceSectionMobile : styles.workspaceSection]}>
        <Section
            title={translate('initialSettingsPage.aboutPage.troubleshoot')}
            isCentralPane
            subtitleMuted
            illustration={LottieAnimations.Desk}
            titleStyles={styles.accountSettingsSectionTitle}
            illustrationBackgroundColor={theme.PAGE_THEMES[SCREENS.SETTINGS.TROUBLESHOOT].backgroundColor}
        >
        <View style={[styles.settingsPageBody, styles.mt5]}>
            <Text style={styles.mb4}>
                <Text>{translate('initialSettingsPage.troubleshoot.description')}</Text>{' '}
                <TextLink
                    style={styles.link}
                    onPress={() => Report.navigateToConciergeChat()}
                >
                    {translate('initialSettingsPage.troubleshoot.submitBug')}
                </TextLink>
            </Text>
        </View>
        <View style={[styles.mr8]}>
            <TestToolRow title="Client side logging">
                <Switch
                    accessibilityLabel="Client side logging"
                    isOn={!!shouldStoreLogs}
                    onToggle={() => (shouldStoreLogs ? Console.disableLoggingAndFlushLogs() : Console.setShouldStoreLogs(true))}
                />
            </TestToolRow>
        </View>
        <MenuItemList
            menuItems={menuItems}
            shouldUseSingleExecution
        />
        {/* Enable additional test features in non-production environments */}
        {!isProduction && (
            <View style={[styles.mr8, styles.mt6]}>
                <TestToolMenu />
            </View>
        )}
        <ConfirmModal
            title={translate('common.areYouSure')}
            isVisible={isConfirmationModalVisible}
            onConfirm={() => {
                setIsConfirmationModalVisible(false);
                Onyx.clear(keysToPreserve).then(() => {
                    App.openApp();
                });
            }}
            onCancel={() => setIsConfirmationModalVisible(false)}
            prompt={translate('initialSettingsPage.troubleshoot.confirmResetDescription')}
            confirmText={translate('initialSettingsPage.troubleshoot.resetAndRefresh')}
            cancelText={translate('common.cancel')}
        />
        </Section>
    </View>
</ScrollView>
</ScreenWrapper>
);

Test branch

https://github.com/ShridharGoel/ExpensifyApp/tree/test-branch-for-38594

Krishna2323 · 2024-03-21T12:01:27Z

Proposal

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

Move "Troubleshoot" out of About and into Settings as its own nav item

What is the root cause of that problem?

New feature

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

Steps we need to follow:

Move the line below from AboutPage to InitialSettingsPage with routeName.

App/src/pages/settings/AboutPage/AboutPage.tsx

Line 91 in 8206580

translationKey: 'initialSettingsPage.aboutPage.troubleshoot',

To:

App/src/pages/settings/InitialSettingsPage.tsx

Line 249 in 8206580

},

Remove SCREENS.SETTINGS.TROUBLESHOOT from places below:

App/src/libs/Navigation/linkingConfig/CENTRAL_PANE_TO_RHP_MAPPING.ts

Line 38 in 8206580

    
           [SCREENS.SETTINGS.ABOUT]: [SCREENS.SETTINGS.APP_DOWNLOAD_LINKS, SCREENS.SETTINGS.TROUBLESHOOT],

App/src/libs/Navigation/AppNavigator/ModalStackNavigators.tsx

Line 229 in 8206580

    
           [SCREENS.SETTINGS.TROUBLESHOOT]: () => require('../../../pages/settings/AboutPage/TroubleshootPage').default as React.ComponentType,

App/src/libs/Navigation/linkingConfig/config.ts

Lines 179 to 181 in 8206580

    
           [SCREENS.SETTINGS.TROUBLESHOOT]: { 
        
               path: ROUTES.SETTINGS_TROUBLESHOOT, 
        
               exact: true,

Add SCREENS.SETTINGS.TROUBLESHOOT mapping to the places below:

App/src/libs/Navigation/AppNavigator/Navigators/CentralPaneNavigator/BaseCentralPaneNavigator.tsx

Line 22 in 8206580

[SCREENS.SETTINGS.ABOUT]: () => require('../../../../../pages/settings/AboutPage/AboutPage').default as React.ComponentType,

App/src/libs/Navigation/types.ts

Line 104 in 8206580

[SCREENS.SETTINGS.ABOUT]: undefined;

App/src/libs/Navigation/types.ts

Line 104 in 8206580

[SCREENS.SETTINGS.ABOUT]: undefined;
We also need to make styling changes

Result

ShridharGoel · 2024-03-21T12:04:08Z

Proposal

Updated with new UI.

ShridharGoel · 2024-03-21T12:08:11Z

Proposal

Updated with link of test branch

tienifr · 2024-03-21T12:08:19Z

Proposal

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

Move TroubleshootPage into the Settings navigation as it's own nav item, and the Troubleshoot UI should look like the About page.

What is the root cause of that problem?

This is new feature request.

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

Small note for reviewer: I was not the first ones to post the proposal, partly because I tried to actually get it working and implementing it locally first, so that I can write a high quality proposals and able to highlight the differences and caveats that we need to take note of (mostly in the 1 part above) instead of rushing to a proposal when I didn't have it actually working and looking like design from my local. If you look into the history you can see I'm the first to have a screenshot of the new page actually working and looking exactly like design, I had to made sure of that before I write the proposal.

Let's craft the new TroubleshootPage UI

Some important notes:

We need to add a new renderSubtitle prop to Section, because for trouble shoot page, the subtitle will contain a hyperlink
There're many different UI elements in the TroubleShootPage, like the TestToolRow, so it's not similar to the AboutPage as above proposal mentioned
We need to supply a Lightbulb illustration as the icon in the Header, currently we don't have that in the app so I temporarily substitute by the black light bulb icon

Move the troubleshoot item here to above the sign out button here
Make sure the navigation works with the TroubleshootPage as an independent page, this part is the same as for the AboutPage

In here, add

[SCREENS.SETTINGS.TROUBLESHOOT]: () => require('../../../../../pages/settings/AboutPage/TroubleshootPage.tsx').default as React.ComponentType,

Update this to

[SCREENS.SETTINGS.ABOUT]: [SCREENS.SETTINGS.APP_DOWNLOAD_LINKS],
[SCREENS.SETTINGS.TROUBLESHOOT]: [SCREENS.SETTINGS.CONSOLE],

In here, add

[SCREENS.SETTINGS.TROUBLESHOOT]: {
    path: ROUTES.SETTINGS_TROUBLESHOOT,
    exact: true,
},

Remove this
In here, add

SCREENS.SETTINGS.TROUBLESHOOT,

It looks completely like design now (except for the light bulb part which I explained above):

Here's the full code for the UI part

return (
        <ScreenWrapper
            shouldEnablePickerAvoiding={false}
            shouldShowOfflineIndicatorInWideScreen
            testID={TroubleshootPage.displayName}
        >
            <HeaderWithBackButton
                title={translate('initialSettingsPage.aboutPage.troubleshoot')}
                shouldShowBackButton={isSmallScreenWidth}
                onBackButtonPress={() => Navigation.goBack(ROUTES.SETTINGS)}
                icon={Expensicons.Lightbulb}
            />
            <ScrollView contentContainerStyle={styles.pt3}>
                <View style={[styles.flex1, isSmallScreenWidth ? styles.workspaceSectionMobile : styles.workspaceSection]}>
                    <Section
                        title={translate('initialSettingsPage.aboutPage.troubleshoot')}
                        subtitle={translate('initialSettingsPage.troubleshoot.description')}
                        isCentralPane
                        subtitleMuted
                        illustration={LottieAnimations.Desk}
                        titleStyles={styles.accountSettingsSectionTitle}
                        illustrationBackgroundColor={theme.PAGE_THEMES[SCREENS.SETTINGS.TROUBLESHOOT].backgroundColor}
                        renderSubtitle={() => <Text style={[styles.mt4]}>
                            <Text>{translate('initialSettingsPage.troubleshoot.description')}</Text>{' '}
                            <TextLink
                                style={styles.link}
                                onPress={() => Report.navigateToConciergeChat()}
                            >
                                {translate('initialSettingsPage.troubleshoot.submitBug')}
                            </TextLink>
                        </Text>}
                    >
                        <View style={[styles.flex1, styles.mt5]}>
                        <View style={[styles.mr8]}>
                                <TestToolRow title="Client side logging">
                                    <Switch
                                        accessibilityLabel="Client side logging"
                                        isOn={!!shouldStoreLogs}
                                        onToggle={() => (shouldStoreLogs ? Console.disableLoggingAndFlushLogs() : Console.setShouldStoreLogs(true))}
                                    />
                                </TestToolRow>
                            </View>
                            <MenuItemList
                                menuItems={menuItems}
                                shouldUseSingleExecution
                            />
                            {!isProduction && (
                                <View style={[styles.mr8, styles.mt6]}>
                                    <TestToolMenu />
                                </View>
                            )}
                            <ConfirmModal
                                title={translate('common.areYouSure')}
                                isVisible={isConfirmationModalVisible}
                                onConfirm={() => {
                                    setIsConfirmationModalVisible(false);
                                    Onyx.clear(keysToPreserve).then(() => {
                                        App.openApp();
                                    });
                                }}
                                onCancel={() => setIsConfirmationModalVisible(false)}
                                prompt={translate('initialSettingsPage.troubleshoot.confirmResetDescription')}
                                confirmText={translate('initialSettingsPage.troubleshoot.resetAndRefresh')}
                                cancelText={translate('common.cancel')}
                            />
                        </View>
                    </Section>
                </View>
            </ScrollView>
        </ScreenWrapper>

What alternative solutions did you explore? (Optional)

NA

ShridharGoel · 2024-03-21T12:24:35Z

Proposal

Updated to polish the UI even more.

ShridharGoel · 2024-03-21T12:26:55Z

Note that I've also added the needed light bulb in Expensicons.tsx, which can be seen in my test branch.

tienifr · 2024-03-21T12:30:01Z

Since this is feature implementation, I'd be happy to provide the full test branch for my proposal upon request (although you can see the full result attached in the proposal from the start) 👍

shubham1206agra · 2024-03-21T12:40:49Z

Proposal

Updated due to people posting complete diff for no reason (which is discouraged), and this is not a good practice.

ghost · 2024-03-21T12:48:21Z

Updated Proposal with test branch since in the initial comment it was asked to be assigned to

alitoshmatov · 2024-06-19T10:55:25Z

@muttmuure This one is ready for payment

shawnborton · 2024-06-19T13:55:42Z

I found another regression with this one: the Troubleshoot page uses white/light text for the status bar text, and thus you can't see the status bar on iOS:

@tienifr @alitoshmatov can you have a look at that please? Thanks!

tienifr · 2024-06-19T15:16:56Z

@shawnborton We will update it to something like below, right?

shawnborton · 2024-06-19T15:20:00Z

Exactly, check every other page in Settings and you will see the expected behavior.

tienifr · 2024-06-19T22:05:01Z

@alitoshmatov PR #44048 to fix #38594 (comment) can be reviewed

alitoshmatov · 2024-07-06T21:11:13Z

#44048 PR was merged and now on staging

melvin-bot · 2024-07-10T10:47:20Z

Reviewing label has been removed, please complete the "BugZero Checklist".

melvin-bot · 2024-07-10T10:47:24Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

fix change the status bar color #44048

If no regressions arise, payment will be issued on 2024-07-17. 🎊

For reference, here are some details about the assignees on this issue:

@alitoshmatov requires payment automatic offer (Reviewer)
@tienifr requires payment automatic offer (Contributor)

melvin-bot · 2024-07-10T10:47:25Z

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[@alitoshmatov] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[@muttmuure] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

melvin-bot · 2024-07-15T20:10:57Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.6-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

fix change the status bar color #44048

If no regressions arise, payment will be issued on 2024-07-22. 🎊

For reference, here are some details about the assignees on this issue:

@alitoshmatov requires payment automatic offer (Reviewer)
@tienifr requires payment automatic offer (Contributor)

melvin-bot · 2024-07-15T20:10:58Z

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[@alitoshmatov] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[@muttmuure] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

alitoshmatov · 2024-07-16T13:37:44Z

Regression test is here

alitoshmatov · 2024-07-16T13:38:44Z

Regression period ends on 17th, pr was merged on 10th

muttmuure · 2024-07-25T12:57:08Z

$500 - @alitoshmatov
$500 - @tienifr

muttmuure · 2024-07-25T12:58:20Z

Paid

shawnborton added the NewFeature Something to build that is a new item. label Mar 19, 2024

melvin-bot bot assigned muttmuure Mar 19, 2024

melvin-bot bot added the Weekly KSv2 label Mar 19, 2024

melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Mar 19, 2024

muttmuure added the External Added to denote the issue can be worked on by a contributor label Mar 21, 2024

melvin-bot bot changed the title ~~Move "Troubleshoot" out of About and into Settings as its own nav item~~ [$500] Move "Troubleshoot" out of About and into Settings as its own nav item Mar 21, 2024

melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Mar 21, 2024

melvin-bot bot assigned alitoshmatov Mar 21, 2024

tienifr mentioned this issue Jun 19, 2024

fix change the status bar color #44048

Merged

50 tasks

melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Jun 19, 2024

melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Jul 10, 2024

melvin-bot bot removed the Reviewing Has a PR in review label Jul 10, 2024

melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Jul 15, 2024

melvin-bot bot added the Overdue label Jul 24, 2024

melvin-bot bot removed the Overdue label Jul 25, 2024

muttmuure closed this as completed Jul 25, 2024

[HOLD for payment 2024-07-17][$500] Move "Troubleshoot" out of About and into Settings as its own nav item #38594

[HOLD for payment 2024-07-17][$500] Move "Troubleshoot" out of About and into Settings as its own nav item #38594

Comments

shawnborton commented Mar 19, 2024 • edited by melvin-bot bot Loading

melvin-bot bot commented Mar 19, 2024

melvin-bot bot commented Mar 19, 2024

allgandalf commented Mar 19, 2024

ghost commented Mar 19, 2024 • edited by ghost Loading

Proposal

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

What is the root cause of that problem?

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

What alternative solutions did you explore? (Optional)

Result :

ADDED TEST BRANCH - https://github.com/godofoutcasts94/App/tree/moving-troubleshoot-page

ghost commented Mar 19, 2024

ghost commented Mar 19, 2024

muttmuure commented Mar 21, 2024

melvin-bot bot commented Mar 21, 2024

melvin-bot bot commented Mar 21, 2024

ghost commented Mar 21, 2024 • edited by ghost Loading

shubham1206agra commented Mar 21, 2024 • edited Loading

Proposal

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

What is the root cause of that problem?

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

What alternative solutions did you explore? (Optional)

ShridharGoel commented Mar 21, 2024 • edited Loading

Proposal

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

What is the root cause of that problem?

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

Test branch

Krishna2323 commented Mar 21, 2024

Proposal

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

What is the root cause of that problem?

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

Result

ShridharGoel commented Mar 21, 2024

Proposal

ShridharGoel commented Mar 21, 2024

Proposal

tienifr commented Mar 21, 2024 • edited Loading

Proposal

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

What is the root cause of that problem?

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

What alternative solutions did you explore? (Optional)

ShridharGoel commented Mar 21, 2024

Proposal

ShridharGoel commented Mar 21, 2024

tienifr commented Mar 21, 2024

shubham1206agra commented Mar 21, 2024

Proposal

ghost commented Mar 21, 2024 • edited by ghost Loading

alitoshmatov commented Jun 19, 2024

shawnborton commented Jun 19, 2024

tienifr commented Jun 19, 2024

shawnborton commented Jun 19, 2024

tienifr commented Jun 19, 2024

alitoshmatov commented Jul 6, 2024

melvin-bot bot commented Jul 10, 2024

melvin-bot bot commented Jul 10, 2024

melvin-bot bot commented Jul 10, 2024

melvin-bot bot commented Jul 15, 2024

melvin-bot bot commented Jul 15, 2024

alitoshmatov commented Jul 16, 2024

alitoshmatov commented Jul 16, 2024

muttmuure commented Jul 25, 2024

muttmuure commented Jul 25, 2024

shawnborton commented Mar 19, 2024 •

edited by melvin-bot bot

Loading

ghost commented Mar 19, 2024 •

edited by ghost

Loading

ghost commented Mar 21, 2024 •

edited by ghost

Loading

shubham1206agra commented Mar 21, 2024 •

edited

Loading

ShridharGoel commented Mar 21, 2024 •

edited

Loading

tienifr commented Mar 21, 2024 •

edited

Loading

ghost commented Mar 21, 2024 •

edited by ghost

Loading