Skip to content

fix:Intacct date grouping fix#1192

Closed
DhaaraniCIT wants to merge 4 commits intopoc-date-groupingfrom
intacct-date-grouping
Closed

fix:Intacct date grouping fix#1192
DhaaraniCIT wants to merge 4 commits intopoc-date-groupingfrom
intacct-date-grouping

Conversation

@DhaaraniCIT
Copy link
Contributor

@DhaaraniCIT DhaaraniCIT commented Feb 27, 2025

Description

fix:Intacct date grouping fix

Clickup

https://app.clickup.com

Screen.Recording.2025-02-27.at.4.41.56.PM.mov
Screen.Recording.2025-02-27.at.4.42.54.PM.mov

Summary by CodeRabbit

  • Refactor

    • Streamlined the configuration for expense date choices in corporate charge card transactions.
    • Simplified the logic to consistently use the spent date option, reducing dynamic variations in date settings.
    • Adjusted date option labels for improved clarity in the user interface.
  • Bug Fixes

    • Removed outdated test cases related to credit card expense grouping date options.
  • Chores

    • Removed environment declaration for the staging deployment in GitHub Actions workflows.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 27, 2025

Walkthrough

This pull request refactors the expense date options handling within the IntacctExportSettingsComponent. The dynamic logic for corporate credit card transactions is simplified by removing assignments and watchers for grouping date options. The method now directly patches the export date to a fixed value, and the construction of reimbursable expense grouping options now leverages a static factory method.

Changes

File Path Change Summary
src/app/integrations/.../intacct-export-settings.component.ts Refactored expense date options logic by removing the assignment of cccExpenseGroupingDateOptions in setCCExpenseDateOptions and commenting out its invocation in cccExportTypeWatcher; removed methods updateCCCGroupingDateOptions and setupCCCGroupingWatcher; updated setupCustomWatchers to use ExportSettingModel.constructExportDateOptions for generating grouping options.
src/app/integrations/.../intacct-export-settings.component.spec.ts Removed test case for updating credit card expense grouping date options; modified expected values in cccExpenseGroupingDateOptions array, changing labels and values for certain options.
.github/workflows/.../c1-staging-deployment.yml Removed environment declaration environment: QA in job staging_deploy.
.github/workflows/.../qa-deployment.yml Removed environment declaration environment: QA in job staging_deploy.

Suggested reviewers

  • ruuushhh

Poem

Hop along, dear coder friend,
I'm a bunny with a joyful blend,
Skipping over watchers gone astray,
Code paths clear for a brighter day,
With carrots and fixes on display! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a412137 and f2dc1b5.

📒 Files selected for processing (2)
  • .github/workflows/c1-staging-deployment.yml (0 hunks)
  • .github/workflows/qa-deployment.yml (0 hunks)
💤 Files with no reviewable changes (2)
  • .github/workflows/c1-staging-deployment.yml
  • .github/workflows/qa-deployment.yml
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: staging_deploy

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the size/M Medium PR label Feb 27, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/app/integrations/intacct/intacct-shared/intacct-export-settings/intacct-export-settings.component.ts (1)

280-280: Consider removing commented-out code or clarifying its purpose.
Retaining commented-out code can cause confusion and lead to maintenance overhead. If you no longer need this line, removing it fully is recommended. Otherwise, add a comment explaining the need to keep it.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f408a04 and 1373667.

📒 Files selected for processing (1)
  • src/app/integrations/intacct/intacct-shared/intacct-export-settings/intacct-export-settings.component.ts (2 hunks)
🔇 Additional comments (2)
src/app/integrations/intacct/intacct-shared/intacct-export-settings/intacct-export-settings.component.ts (2)

464-464: Looks good; verify correctness of constructed date options.
This updated approach to build reimbursableExpenseGroupingDateOptions via constructExportDateOptions() seems consistent with the refactor. As a sanity check, confirm the returned options meet all use cases for reimbursable expenses.


468-471: Straightforward logic for cccExpenseGroupingDateOptions.
Passing true for CHARGE_CARD_TRANSACTION and false otherwise aligns with the new simplified approach. This indicates a clear separation of credit card date-grouping behavior versus reimbursable behavior.

private cccExportTypeWatcher(): void {
this.exportSettingsForm.controls.cccExportType.valueChanges.subscribe((isCCCExportTypeSelected) => {
this.setCCExpenseDateOptions(isCCCExportTypeSelected);
// This.setCCExpenseDateOptions(isCCCExportTypeSelected);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cann we remove this instead of commenting

@DhaaraniCIT DhaaraniCIT added staging_deploy Triggers deployment of active branch to Staging c1_qa_deploy Deploys to QA env labels Feb 28, 2025
@DhaaraniCIT DhaaraniCIT added c1_qa_deploy Deploys to QA env and removed c1_qa_deploy Deploys to QA env labels Feb 28, 2025
@github-actions
Copy link

Unit Test Coverage % values
Statements 32.92% ( 4146 / 12594 )
Branches 26.35% ( 1174 / 4454 )
Functions 25.48% ( 889 / 3488 )
Lines 33.1% ( 4081 / 12326 )

@Hrishabh17 Hrishabh17 closed this Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c1_qa_deploy Deploys to QA env size/M Medium PR staging_deploy Triggers deployment of active branch to Staging

Development

Successfully merging this pull request may close these issues.

3 participants