[QBD] [Import] Classes page #50680

hoangzinh · 2024-10-12T09:46:04Z

Details

Fixed Issues

$ #49704
PROPOSAL:

Tests

Same as QA steps

Verify that no errors appear in the JS console

Offline tests

Same as QA steps

QA Steps

Prerequisites:

Turn on Beta quickbooksDesktopOnNewDot on your account
Connect your workspace to QBD in OldDot. (Help doc)

Sign in on an account above
Go to any Workspace -> Accounting
Click on "Import" menu under QuickBooks Desktop connection
Click on "Classes" menu item
Verify it displays 1 "Import" toggle button and "Displayed as" menu
Switch on "Import" toggle button
Verify it saves successfully to the server and the "Displayed as" value is "Tags"
Click on "Displayed as"
Change to "Report fields"
Verify it saves successfully to the server and the "Displayed as" value is "Report fields"

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-10-14.at.22.46.45.mov

Android: mWeb Chrome

Screen.Recording.2024-10-14.at.22.35.18.android.chrome.mov

iOS: Native

Screen.Recording.2024-10-14.at.22.39.31.ios.mov

iOS: mWeb Safari

Screen.Recording.2024-10-14.at.22.37.24.ios.safari.mov

MacOS: Chrome / Safari

Screen.Recording.2024-10-14.at.21.19.53.web.mov

MacOS: Desktop

Screen.Recording.2024-10-14.at.22.32.04.desktop.mov

hoangzinh · 2024-10-12T09:47:10Z

Hi @lakchote when you have time, can you help to check if I call API UpdateQuickbooksDesktopSyncClasses correct? It always returns mapping value "NONE" when I can this API to update sync classes

Screen.Recording.2024-10-12.at.16.43.15.mov

lakchote · 2024-10-14T08:19:11Z

Hi @lakchote when you have time, can you help to check if I call API UpdateQuickbooksDesktopSyncClasses correct? It always returns mapping value "NONE" when I can this API to update sync classes

Hmm, I've verified and it works correctly with cURL request. It looks like the default value for settingValue is used.

Here's how it looks like in Postman:

Could you try it?

hoangzinh · 2024-10-14T11:32:56Z

Hmm, I've verified and it works correctly with cURL request. It looks like the default value for settingValue is used.

@lakchote yes, I just tested. Confirmed that it works if I use staging server but not in production.

lakchote · 2024-10-14T13:44:59Z

Hmm, I've verified and it works correctly with cURL request. It looks like the default value for settingValue is used.

@lakchote yes, I just tested. Confirmed that it works if I use staging server but not in production.

The PR hasn't been deployed on production yet, that explains why.

hoangzinh · 2024-10-14T15:39:00Z

src/languages/es.ts

+            tagsDisplayedAsDescription: 'Nivel de partida',
+            reportFieldsDisplayedAsDescription: 'Nivel de informe',


Copied here

App/src/languages/es.ts

Lines 2362 to 2363 in 1535588

lineItemLevel: 'Nivel de partida',

reportLevel: 'Nivel de informe',

melvin-bot · 2024-10-14T15:49:27Z

@Pujan92 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]

hoangzinh · 2024-10-14T15:50:13Z

Oops sorry @Pujan92. @ZhenjaHorbach will review this issue as it's a part of in QBD project

src/pages/workspace/accounting/qbd/import/QuickbooksDesktopClassesPage.tsx

ZhenjaHorbach · 2024-10-14T16:34:28Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (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
- 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 verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
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
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- 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)
- Any 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)
- All JSX used for rendering exists in the render method
- The 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
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 have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

android.mov

Android: mWeb Chrome

android-web.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ios-web.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

ZhenjaHorbach · 2024-10-14T18:15:51Z

LGTM !

OSBotify · 2024-10-15T06:33:25Z

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

github-actions · 2024-10-17T02:00:02Z

🚀 Deployed to staging by https://github.com/lakchote in version: 9.0.50-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

github-actions · 2024-10-18T18:48:52Z

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.50-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

hoangzinh added 2 commits October 12, 2024 15:27

Setup screen & route configs

801f463

Sync classes config

551ffd4

Select displayed as page

b8603d7

Update es translation

53888cd

Fix bug request with double code

c843618

hoangzinh added 2 commits October 14, 2024 21:14

Correct subscribe list

53042de

Merge branch 'main' into 49704-qbd-import-classes

1c00823

hoangzinh commented Oct 14, 2024

View reviewed changes

hoangzinh marked this pull request as ready for review October 14, 2024 15:49

hoangzinh requested a review from a team as a code owner October 14, 2024 15:49

melvin-bot bot requested review from Pujan92 and removed request for a team October 14, 2024 15:49

ZhenjaHorbach reviewed Oct 14, 2024

View reviewed changes

src/pages/workspace/accounting/qbd/import/QuickbooksDesktopClassesPage.tsx Outdated Show resolved Hide resolved

Use correct clear function

cf95e3d

ZhenjaHorbach approved these changes Oct 14, 2024

View reviewed changes

melvin-bot bot requested a review from lakchote October 14, 2024 18:16

lakchote approved these changes Oct 15, 2024

View reviewed changes

lakchote merged commit 192070f into Expensify:main Oct 15, 2024
17 of 18 checks passed

github-actions bot mentioned this pull request Oct 17, 2024

Deploy Checklist: New Expensify 2024-10-17 #50969

Closed

90 tasks

melvin-bot bot mentioned this pull request Oct 18, 2024

[HOLD for payment 2024-10-25] [Wave Control] [QBD] [Import] Classes page #49704

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[QBD] [Import] Classes page #50680

[QBD] [Import] Classes page #50680

hoangzinh commented Oct 12, 2024 •

edited

Loading

hoangzinh commented Oct 12, 2024 •

edited

Loading

lakchote commented Oct 14, 2024

hoangzinh commented Oct 14, 2024

lakchote commented Oct 14, 2024

hoangzinh Oct 14, 2024

melvin-bot bot commented Oct 14, 2024

hoangzinh commented Oct 14, 2024

ZhenjaHorbach commented Oct 14, 2024 •

edited

Loading

ZhenjaHorbach commented Oct 14, 2024

OSBotify commented Oct 15, 2024

github-actions bot commented Oct 17, 2024

github-actions bot commented Oct 18, 2024

		tagsDisplayedAsDescription: 'Nivel de partida',
		reportFieldsDisplayedAsDescription: 'Nivel de informe',

	lineItemLevel: 'Nivel de partida',
	reportLevel: 'Nivel de informe',

[QBD] [Import] Classes page #50680

[QBD] [Import] Classes page #50680

Conversation

hoangzinh commented Oct 12, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

hoangzinh commented Oct 12, 2024 • edited Loading

lakchote commented Oct 14, 2024

hoangzinh commented Oct 14, 2024

lakchote commented Oct 14, 2024

hoangzinh Oct 14, 2024

Choose a reason for hiding this comment

melvin-bot bot commented Oct 14, 2024

hoangzinh commented Oct 14, 2024

ZhenjaHorbach commented Oct 14, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

ZhenjaHorbach commented Oct 14, 2024

OSBotify commented Oct 15, 2024

github-actions bot commented Oct 17, 2024

github-actions bot commented Oct 18, 2024

hoangzinh commented Oct 12, 2024 •

edited

Loading

hoangzinh commented Oct 12, 2024 •

edited

Loading

ZhenjaHorbach commented Oct 14, 2024 •

edited

Loading