build: run unit tests on new PRs #1038
Conversation
WalkthroughYo, check it! This pull request's all about the Changes
Possibly related PRs
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (3)
.github/workflows/unit-test.yml (2)
1-5: Yo, listen up! This workflow's name is tight, no doubt!The name "Unit Test" is straight to the point, just like my rhymes.
But check it, we got some extra spaces after those commas, it's crime time!Let's clean up those spaces, make it look real nice:
- types: [assigned, opened, synchronize, reopened] + types: [assigned, opened, synchronize, reopened]Now it's clean like my lyrics, no need to rehearse!
🧰 Tools
🪛 yamllint
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
28-35: Aight, let's talk about that coverage game, it's lookin' tight!You're droppin' that coverage like hot bars on a track,
Commentin' and uploadin', got your tests on lock, that's a fact!
But yo, one small tweak could make this flow even slicker,
Add a name to that Codecov step, make it quicker to figure!Here's a little remix to make it pop:
- name: Upload coverage to Codecov uses: codecov/codecov-action@v3 + with: + name: codecov-umbrella + fail_ci_if_error: trueNow we're failin' if Codecov trips, that's how we roll,
Keepin' our code coverage game on swole!package.json (1)
Line range hint
1-105: Yo, let's talk about keepin' our crew fresh!Listen up, my dev homies, I got a flow for you to follow:
Keep them dependencies updated, don't let 'em get hollow.
Security's tight, performance is key,
So check your versions periodically.npm audit, yarn upgrade, whatever your style,
Just make sure you're on top of that dependency pile.
It ain't glamorous, but it's part of the grind,
Keepin' our code base safe and refined.What say you, squad? Wanna set up a regular beat,
To review and upgrade, keep our project elite?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
- .github/workflows/unit-test.yml (1 hunks)
- package.json (1 hunks)
🧰 Additional context used
🪛 actionlint
.github/workflows/unit-test.yml
14-14: the runner of "actions/setup-node@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
🪛 yamllint
.github/workflows/unit-test.yml
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
[error] 22-22: trailing spaces
(trailing-spaces)
🔇 Additional comments (3)
.github/workflows/unit-test.yml (2)
12-18:⚠️ Potential issueYo, we're usin' ancient scrolls for our Node setup, dawg!
Listen up, 'cause this beat's important:
Our actions are old, performance's distorted!
We're rockin' v1 like it's still 2019,
But in the tech game, that's ancient history!Let's upgrade our flow, make it fresh and new:
- - uses: actions/checkout@v1 + - uses: actions/checkout@v4 - - name: Setup GitHub Action - uses: actions/setup-node@v1 + - name: Setup Node.js + uses: actions/setup-node@v3 with: - node-version: 22.2.0 + node-version: 18.xNow about that Node version, 22.2.0's blazin' hot,
But for stability, it might not be the best shot.
Let's roll back to LTS, keep our builds from crashin',
18.x is solid, keeps our tests always passin'!Yo, let's make sure our deps can handle this switch:
#!/bin/bash # Check if package.json specifies a Node version grep '"node":' package.json # List out our dependencies jq '.dependencies' package.jsonIf it all checks out, we're ready to spit these new rhymes!
🧰 Tools
🪛 actionlint
14-14: the runner of "actions/setup-node@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
19-27: Yo, these env vars are faker than a wack MC's flow!We're settin' up the stage for our tests to shine,
But these env vars? They ain't lookin' so fine!
"lolo" and "http://lolo.fyle.tech"? That's just for show,
In production, that kinda stuff's gotta go!Let's make sure we ain't leakin' no secrets, you feel me?
#!/bin/bash # Check if we got any real secrets in our config rg -i '(api_key|secret|password)' .github/workflowsIf it's clean, then we cool. But remember this rhyme:
Real values in CI/CD? That's a security crime!You want me to spit some bars on how to use GitHub secrets?
Keep your creds safe, away from prying eyes that seek it?
Just say the word, and I'll drop that knowledge bomb,
Show you how to keep your workflow secure and calm!🧰 Tools
🪛 yamllint
[error] 22-22: trailing spaces
(trailing-spaces)
package.json (1)
10-10: Yo, check it, we got a new beat in this track!Listen up, homies! We just dropped a fresh line in this script,
Adding some flavor before the tests get ripped.
Thatsetup:brandingcommand's now in the mix,
Making sure our style's on point, no need to fix.It's all about that CI flow, you feel me?
Running tests smooth, that's the real G.
| jobs: | ||
| unit-test: | ||
| permissions: write-all | ||
| runs-on: ubuntu-latest |
There was a problem hiding this comment.
💡 Codebase verification
Yo, unit-test.yml, permissions way too broad,
Write-all's a stretch, it's a security fraud.
Let's slim it down, keep it precise,
Lock it down tight, make it nice.
- permissions: write-all
+ permissions:
+ contents: read
+ checks: write🔗 Analysis chain
Yo, hold up! We're givin' out permissions like they're free CDs!
The job setup's lookin' good, no lie,
But them permissions, they're set sky-high!
"write-all" for unit tests? That's overkill, my friend,
Let's lock it down, make security transcend!
Check if we really need all them write perms, ya dig?
Maybe we can slim it down, make it not so big.
If it comes back clean, let's tighten up our act:
- permissions: write-all
+ permissions:
+ contents: read
+ checks: write # Needed for test resultsNow that's a flow that's secure and slick!
Yo, check it, we gotta keep it tight,
Permissions on point, make sure it's right.
Unit tests don’t need all the write,
Let’s scope it down, keep the flow in sight.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Let's see what other workflows are usin' for permissions
rg -i 'permissions:' .github/workflows
Length of output: 5891
Script:
#!/bin/bash
# Extracting permissions from all GitHub workflow files
rg -i '^permissions:' .github/workflows --context 2
Length of output: 520
There was a problem hiding this comment.
Actionable comments posted: 5
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (9)
- .github/workflows/unit-test.yml (1 hunks)
- karma.conf.js (1 hunks)
- src/app/core/interceptor/jwt.interceptor.spec.ts (1 hunks)
- src/app/core/services/bamboo-hr/bamboo-hr.service.spec.ts (1 hunks)
- src/app/core/services/common/api.service.spec.ts (1 hunks)
- src/app/core/services/common/auth.service.spec.ts (1 hunks)
- src/app/core/services/common/clone-setting.service.spec.ts (1 hunks)
- src/app/core/services/org/org.service.spec.ts (1 hunks)
- src/app/core/services/travelperk/travelperk.service.spec.ts (1 hunks)
🧰 Additional context used
🪛 actionlint
.github/workflows/unit-test.yml
14-14: the runner of "actions/setup-node@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
🪛 yamllint
.github/workflows/unit-test.yml
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
[error] 22-22: trailing spaces
(trailing-spaces)
🔇 Additional comments (9)
src/app/core/services/common/clone-setting.service.spec.ts (1)
11-11: Yo, check it, we got a URL switch-up!Listen up, homies! We just flipped the script on that API_BASE_URL,
Swappin' out that old 'api_url' for the fresh 'cluster_domain_api_url', it's true.
It's all part of the master plan, to keep our tests in sync,
With the new environment setup, so our code don't stink!This change is tight, it's right, it's outta sight!
Keepin' our tests aligned, yeah, that's how we do it right!.github/workflows/unit-test.yml (3)
1-5: Yo, this workflow's lit, no need to quit!The name's on point, the trigger's tight,
For pull requests, it's ready to fight.🧰 Tools
🪛 yamllint
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
[warning] 5-5: too many spaces after comma
(commas)
7-10: Yo, listen up, we gotta tighten this ship!Permissions wide open like 8 Mile,
But for unit tests, that ain't our style.
Let's lock it down, make it lean and mean,
Only what we need, keep our repo clean.Here's how we flip the script:
- permissions: write-all + permissions: + contents: read + checks: writeNow we're rollin' with the real slim permissions, ya dig?
28-35: Yo, this coverage game is tight, shinin' bright like a spotlight!Commentin' on PRs, uploadin' to Codecov,
This setup's complete, givin' tests mad love.
Keep that quality high, let the numbers speak,
This workflow's a banger, straight up on fleek!src/app/core/services/common/auth.service.spec.ts (1)
14-14: Yo, check it out! We're switchin' up the API game!Listen up, homies! We just flipped the script on that
API_BASE_URL. Now we're rockin' withenvironment.cluster_domain_api_urlinstead of that old schoolapi_url. It's all about stayin' fresh and keepin' our tests in sync with the rest of the crew. This change is tight, it's right, and it's gonna make our auth flow shine bright!src/app/core/services/bamboo-hr/bamboo-hr.service.spec.ts (1)
14-14: Yo, listen up! This change is straight fire!Aight, so we switched up the API_BASE_URL, now it's hittin' that cluster_domain_api_url instead of the old api_url. That's a smart move, keepin' it consistent with the other test suites. But yo, we gotta make sure this new URL is legit in the environment config, you feel me?
Let's run this script to check if the new URL is set up right:
If it don't show up, we might need to add it to the environment files, you dig?
src/app/core/services/travelperk/travelperk.service.spec.ts (2)
Line range hint
1-158: Listen up, y'all! We gotta keep our eyes on the prize!Now that we've flipped the script on our API_BASE_URL
We gotta make sure every test case is singin' the same tune
From getTravelperkData to connect, every single one
Better be usin' that new URL, or we ain't doneSo here's what we gotta do, no time to pause
Run through each test, check them HTTP calls
Make sure they're all hittin' that new cluster domain
'Cause if they ain't, our tests gonna be a painLet's drop this beat and check our work, yo:
#!/bin/bash # We're gonna find all them HTTP calls and make sure they're usin' the new URL rg "url: `\${API_BASE_URL}" src/app/core/services/travelperk/travelperk.service.spec.tsIf all our calls are usin' the new URL, we're golden
If not, we gotta fix 'em up, no time for holdin'
14-14: Yo, listen up! This change is straight fire!Aight, check it out, we're switchin' up the game
From api_url to cluster_domain, ain't it plain?
This change is crucial, don't you dare ignore
It's gonna affect all our HTTP calls, that's for sureLet's make sure this change is consistent, yo:
✅ Verification successful
Yo, let's drop that glitch and make this script tight:
All Set: API_BASE_URL Updated Right
Yo, checked the lines, all set tight.
API_BASE_URL's shining bright.
No issues found, code's legit.
Good job team, now let's commit.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Yo, we're checkin' if all the homies are using the same API_BASE_URL rg "API_BASE_URL.*environment\.cluster_domain_api_url" --type tsLength of output: 93
Script:
#!/bin/bash # Check if all instances use the updated API_BASE_URL rg "API_BASE_URL\s*=\s*environment\.cluster_domain_api_url" --type tsLength of output: 855
src/app/core/interceptor/jwt.interceptor.spec.ts (1)
20-20: Yo, listen up! We're switchin' up the game plan!Aight, so we're flippin' the script on that API_BASE_URL, ya feel me?
From api_url to cluster_domain_api_url, that's the new beat we're droppin'.
It's all part of the master plan, keepin' it consistent across the board.But yo, before we call it a wrap, make sure them tests ain't trippin'.
Run 'em again, make sure they still spittin' fire, not throwin' errors.
'Cause if somethin's off, we gotta catch it before it wrecks the whole flow.Here's a little somethin' to help you check if everything's still tight:
✅ Verification successful
Change Verified: All Tests Passed
Yo, tests came back clean, not a single failin' line,
API_BASE_URL switched up, everything's fine.
No bugs in sight, we're ridin' smooth,
This change is locked down, it’s got the groove.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Yo, let's see if our tests are still kickin' it # First, let's peep how many tests we got total_tests=$(grep -c "it(" src/app/core/interceptor/jwt.interceptor.spec.ts) # Now, let's run them tests and see what's good npm test src/app/core/interceptor/jwt.interceptor.spec.ts > test_output.txt 2>&1 # Check if any tests failed failed_tests=$(grep -c "FAILED" test_output.txt) echo "Total tests: $total_tests" echo "Failed tests: $failed_tests" if [ $failed_tests -eq 0 ]; then echo "All tests passed! We're golden!" else echo "Yo, we got $failed_tests failed tests. Better check that output!" fi # Clean up rm test_output.txtLength of output: 387
| - name: Setup GitHub Action | ||
| uses: actions/setup-node@v1 | ||
| with: | ||
| node-version: 22.2.0 |
There was a problem hiding this comment.
Yo, we gotta upgrade this beat, make it elite!
Node version's fresh, but the action's old news,
Time to level up, can't afford to lose.
Let's bump it up, make it crisp and clean,
v3's the latest, know what I mean?
Here's the remix:
- - uses: actions/setup-node@v1
+ - uses: actions/setup-node@v3
with:
node-version: 22.2.0Now we're droppin' beats with the latest heat!
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - name: Setup GitHub Action | |
| uses: actions/setup-node@v1 | |
| with: | |
| node-version: 22.2.0 | |
| - name: Setup GitHub Action | |
| uses: actions/setup-node@v3 | |
| with: | |
| node-version: 22.2.0 |
🧰 Tools
🪛 actionlint
14-14: the runner of "actions/setup-node@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue
(action)
| run: npm run unit_test:ci | ||
| env: | ||
| FYLE_CLIENT_ID: "lolo" | ||
| CALLBACK_URI: "http://lolo.fyle.tech/callback" | ||
| CLUSTER_DOMAIN_API_URL: "http://lolo.fyle.tech" | ||
| FYLE_APP_URL: "http://lolo.fyle.tech" | ||
| SI_API_URL: "http://lolo.fyle.tech" | ||
| SAGE300_API_URL: "http://lolo.fyle.tech" | ||
| - name: Unit Test Coverage |
There was a problem hiding this comment.
Yo, these env vars are like an open mic, we gotta secure this cipher!
Test command's tight, but them vars are exposed,
"lolo" ain't secure, that's just how it goes.
We need some real placeholders, somethin' strong,
So our secrets stay safe, where they belong.
Let's flip this script, make it more discrete:
env:
- FYLE_CLIENT_ID: "lolo"
- CALLBACK_URI: "http://lolo.fyle.tech/callback"
- CLUSTER_DOMAIN_API_URL: "http://lolo.fyle.tech"
- FYLE_APP_URL: "http://lolo.fyle.tech"
- SI_API_URL: "http://lolo.fyle.tech"
- SAGE300_API_URL: "http://lolo.fyle.tech"
+ FYLE_CLIENT_ID: ${{ secrets.FYLE_CLIENT_ID }}
+ CALLBACK_URI: ${{ secrets.CALLBACK_URI }}
+ CLUSTER_DOMAIN_API_URL: ${{ secrets.CLUSTER_DOMAIN_API_URL }}
+ FYLE_APP_URL: ${{ secrets.FYLE_APP_URL }}
+ SI_API_URL: ${{ secrets.SI_API_URL }}
+ SAGE300_API_URL: ${{ secrets.SAGE300_API_URL }}Now we're keepin' our secrets under wraps, like a true lyrical assassin!
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - name: Test | |
| run: npm run unit_test:ci | |
| env: | |
| FYLE_CLIENT_ID: "lolo" | |
| CALLBACK_URI: "http://lolo.fyle.tech/callback" | |
| CLUSTER_DOMAIN_API_URL: "http://lolo.fyle.tech" | |
| FYLE_APP_URL: "http://lolo.fyle.tech" | |
| SI_API_URL: "http://lolo.fyle.tech" | |
| SAGE300_API_URL: "http://lolo.fyle.tech" | |
| - name: Test | |
| run: npm run unit_test:ci | |
| env: | |
| FYLE_CLIENT_ID: ${{ secrets.FYLE_CLIENT_ID }} | |
| CALLBACK_URI: ${{ secrets.CALLBACK_URI }} | |
| CLUSTER_DOMAIN_API_URL: ${{ secrets.CLUSTER_DOMAIN_API_URL }} | |
| FYLE_APP_URL: ${{ secrets.FYLE_APP_URL }} | |
| SI_API_URL: ${{ secrets.SI_API_URL }} | |
| SAGE300_API_URL: ${{ secrets.SAGE300_API_URL }} |
🧰 Tools
🪛 yamllint
[error] 22-22: trailing spaces
(trailing-spaces)
| lines: 50 | ||
| } | ||
| } | ||
| ] |
There was a problem hiding this comment.
💡 Codebase verification
Yo, coverage ain't fully ghosted, still chillin' in codecov.yml and Angular's file. We gotta clear it out everywhere to keep our standards tight.
🔗 Analysis chain
Yo, listen up! We just dropped the beat on coverage checks!
Aight, so we just cut out them coverage thresholds like we're cuttin' tracks,
But hold up, we gotta make sure our code don't fall through the cracks.
Without them checks, our quality might slip, that's the real talk,
So we need a new plan to keep our code tight, let it walk the walk.
Yo, run this script and let's see what's really goin' down:
If you want me to spit some bars 'bout how to keep our code coverage tight without them built-in checks, just holler. I got flows for days on this testing game!
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Let's dig deep and see if we got coverage checks elsewhere
# Check if we got any other files settin' up them thresholds
rg -i 'coverage|threshold' --type yaml --type json
# Peep if we got any CI scripts that might be handlin' this
fd -e yml -e yaml -e json | xargs rg -i 'coverage|threshold'
Length of output: 2821
| }; | ||
|
|
||
| const API_BASE_URL = environment.api_url; | ||
| const API_BASE_URL = environment.cluster_domain_api_url; |
There was a problem hiding this comment.
💡 Codebase verification
Hold up! There's a mismatch in the URLs dropping in the codebase!
- Multiple files are still rockin' the old
api_url, while some switched tocluster_domain_api_url. - Consistency is missing, and this can mess with the flow of your API calls.
🔗 Analysis chain
Yo, listen up! We got a change in the beat, switchin' up that API_BASE_URL!
Aight, so we're flippin' the script from environment.api_url to environment.cluster_domain_api_url. This ain't no small-time hustle, it's a big league move that's gonna echo through the whole damn codebase!
Let's drop this beat and see how far this change goes:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Yo, we're huntin' for all the spots where this new URL's droppin'
echo "Aight, let's see where this new cluster_domain_api_url's poppin' up:"
rg "cluster_domain_api_url" --type ts
echo "\nNow, let's check if there's any old api_url still lingerin' around:"
rg "api_url" --type ts
echo "\nFinally, let's peep into that environment file and see what's really goin' down:"
cat $(fd -t f "environment.ts$")
Length of output: 4762
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
src/app/app.component.spec.ts (1)
15-15: TestBed's got a new beat, but let's make it neat!Yo, check it, we're upgradin' the TestBed configuration,
Added ToastModule and RouterModule to the foundation.
But listen up, I got a small suggestion to make,
Let's break it down, give each import its own line, for goodness sake!Here's how we can make it pop:
- RouterTestingModule, ToastModule, RouterModule + RouterTestingModule, + ToastModule, + RouterModuleIt's just a style thing, to keep our code clean,
Makes it easier to read, know what I mean?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (11)
- src/app/app.component.spec.ts (2 hunks)
- src/app/integrations/intacct/intacct-main/intacct-dashboard/intacct-dashboard.component.spec.ts (1 hunks)
- src/app/integrations/intacct/intacct-main/intacct-export-log/intacct-export-log.component.spec.ts (1 hunks)
- src/app/integrations/intacct/intacct-main/intacct-mapping/intacct-mapping.component.spec.ts (1 hunks)
- src/app/integrations/intacct/intacct-onboarding/intacct-onboarding.component.spec.ts (1 hunks)
- src/app/integrations/intacct/intacct-shared/intacct-advanced-settings/intacct-advanced-settings.component.spec.ts (1 hunks)
- src/app/integrations/intacct/intacct-shared/intacct-export-settings/intacct-export-settings.component.spec.ts (1 hunks)
- src/app/integrations/intacct/intacct.component.spec.ts (1 hunks)
- src/app/integrations/qbd/qbd-main/qbd-main.component.spec.ts (1 hunks)
- src/app/integrations/qbd/qbd-onboarding/qbd-onboarding.component.spec.ts (1 hunks)
- src/app/integrations/qbo/qbo.component.spec.ts (1 hunks)
✅ Files skipped from review due to trivial changes (10)
- src/app/integrations/intacct/intacct-main/intacct-dashboard/intacct-dashboard.component.spec.ts
- src/app/integrations/intacct/intacct-main/intacct-export-log/intacct-export-log.component.spec.ts
- src/app/integrations/intacct/intacct-main/intacct-mapping/intacct-mapping.component.spec.ts
- src/app/integrations/intacct/intacct-onboarding/intacct-onboarding.component.spec.ts
- src/app/integrations/intacct/intacct-shared/intacct-advanced-settings/intacct-advanced-settings.component.spec.ts
- src/app/integrations/intacct/intacct-shared/intacct-export-settings/intacct-export-settings.component.spec.ts
- src/app/integrations/intacct/intacct.component.spec.ts
- src/app/integrations/qbd/qbd-main/qbd-main.component.spec.ts
- src/app/integrations/qbd/qbd-onboarding/qbd-onboarding.component.spec.ts
- src/app/integrations/qbo/qbo.component.spec.ts
🧰 Additional context used
🔇 Additional comments (2)
src/app/app.component.spec.ts (2)
5-6: Yo, these imports are straight fire!Listen up, homies! We're droppin' some fresh modules in the mix,
ToastModule and RouterModule, they're the perfect fix.
Angular best practices? Yeah, we're keepin' it tight,
These imports are placed just right, aight?
Line range hint
1-38: Alright, let's wrap this up like a sick rhyme!Listen up, y'all, 'cause I'm about to spit,
This test file's changes? They're legit!
We added some modules, made the TestBed tight,
Now our app component tests gonna shine bright.The changes are solid, no need to rewrite,
They match the PR's goal, everything's alright.
So let's push this forward, get it in the mix,
'Cause these updates? They're gonna be lit!
1 participant
Clickup
https://app.clickup.com/1864988/v/l/1rx8w-41316
Summary by CodeRabbit
IntacctC1ImportSettingsComponent,IntacctImportSettingsComponent,QbdMappingTableComponent,IntacctDashboardComponent,IntacctExportLogComponent,IntacctMappingComponent,IntacctOnboardingComponent,IntacctAdvancedSettingsComponent,IntacctExportSettingsComponent,IntacctComponent,QbdMainComponent,QbdOnboardingComponent, andQboComponent.