Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Intacct connector page info box for fyle theme #991

Merged
merged 3 commits into from
Oct 1, 2024

Conversation

DhaaraniCIT
Copy link
Contributor

@DhaaraniCIT DhaaraniCIT commented Oct 1, 2024

Description

Adding a Info box for the Intacct connector page similar to the C1 env

Clickup

https://app.clickup.com/t/86cwnfg30

Screenshot 2024-10-01 at 2 41 37 PM

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Enhanced integration configuration for accounting systems, including detailed labels and instructions for NetSuite, Xero, Sage Intacct, and QuickBooks Online.
    • Improved user interface for the Sage Intacct connection form with tailored messages and visual cues based on branding configuration.
    • Expanded customization options for corporate card expenses, including default values and scheduling automatic exports.
  • Bug Fixes

    • Improved validation messages for input fields to enhance user experience.

Copy link
Contributor

coderabbitai bot commented Oct 1, 2024

Walkthrough

The changes involve comprehensive updates to the configuration settings for various accounting integrations, including enhancements to the c1Contents and fyleContents configuration objects. Modifications include the addition of new properties, detailed sub-labels, and improved user instructions across multiple accounting platforms. Additionally, the ContentConfiguration type is updated to support these enhancements, while the HTML structure of the intacct-connector.component.html file is refined for better user experience and clarity.

Changes

Files Change Summary
src/app/branding/c1-contents-config.ts, src/app/branding/fyle-contents-config.ts Updates to configuration objects for various accounting integrations, adding labels, sub-labels, and export settings.
src/app/core/models/branding/content-configuration.model.ts Modifications to the ContentConfiguration type, adding new properties for the Intacct integration.
src/app/shared/components/si/core/intacct-connector/intacct-connector.component.html Modifications to HTML structure, conditional styling, loading state management, and validation messages.

Possibly related PRs

  • intacct code prepend #936: The changes in this PR involve modifications to the Configuration type and the ImportSettings class, which may relate to the enhancements in the c1Contents configuration for managing corporate card expenses in the main PR.
  • feat: intacct code prepend fixes #965: This PR includes updates to the IntacctDashboardComponent and IntacctBaseMappingComponent, which involve handling accepted code fields that are relevant to the integration settings expanded in the main PR.

Suggested labels

c1_staging_deploy, size/S

Suggested reviewers

  • ashwin1111
  • abhishek1234321

Poem

In the code where bunnies hop,
Changes made, we’ll never stop.
With colors bright and loaders near,
Our forms now shine, let’s give a cheer!
Hopping through each line with glee,
A better UI for you and me! 🐇✨


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 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/XS Extra Small PR label Oct 1, 2024
Copy link

github-actions bot commented Oct 1, 2024

PR title must start with "fix:", "feat:", "chore:", "refactor", or "test:" (case-insensitive)

Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

@DhaaraniCIT DhaaraniCIT changed the title chore : Intacct connector page info box for fyle theme chore: Intacct connector page info box for fyle theme Oct 1, 2024
Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

2 similar comments
Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

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

🧹 Outside diff range and nitpick comments (2)
src/app/shared/components/si/core/intacct-connector/intacct-connector.component.html (2)

37-41: LGTM! Consider adding an aria-label for accessibility.

The addition of this information box is a great improvement to the user interface, aligning well with the PR objective. The conditional styling based on the branding configuration ensures visual consistency.

Consider adding an aria-label to the div for improved accessibility:

- <div class="tw-w-400-px tw-py-8-px tw-px-16-px tw-rounded-6-px" [ngClass]="{'tw-bg-bg-tertiary-lighter tw-border tw-border-separator' : brandingConfig.brandId === 'co', 'tw-bg-info-section' : brandingConfig.brandId !== 'co'}">
+ <div class="tw-w-400-px tw-py-8-px tw-px-16-px tw-rounded-6-px" [ngClass]="{'tw-bg-bg-tertiary-lighter tw-border tw-border-separator' : brandingConfig.brandId === 'co', 'tw-bg-info-section' : brandingConfig.brandId !== 'co'}" aria-label="Integration credentials reminder">

Line range hint 1-41: Overall implementation looks great! Consider unifying error message structure.

The Intacct connector component is well-structured with proper conditional rendering, branding configuration, and form validation. Great job on implementing the new info box and maintaining consistency with the existing code.

For improved consistency, consider unifying the structure of error messages. Currently, the Company ID and User ID error messages use "Invalid" while the Password error message uses "Incorrect". Standardizing these messages could enhance the user experience:

- Invalid {{brandingContent.intacct.common.companyId}}. Enter valid {{brandingContent.intacct.common.companyId}}.
+ Invalid {{brandingContent.intacct.common.companyId}}. Please enter a valid {{brandingContent.intacct.common.companyId}}.

- Invalid {{brandingContent.intacct.common.userId}}. Enter valid {{brandingContent.intacct.common.userId}}.
+ Invalid {{brandingContent.intacct.common.userId}}. Please enter a valid {{brandingContent.intacct.common.userId}}.

- Incorrect {{brandingContent.intacct.common.password}}. Enter correct {{brandingContent.intacct.common.password}}.
+ Invalid {{brandingContent.intacct.common.password}}. Please enter a valid {{brandingContent.intacct.common.password}}.

This change would make the error messages more consistent and user-friendly.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c757aaf and a7bd5c9.

📒 Files selected for processing (1)
  • src/app/shared/components/si/core/intacct-connector/intacct-connector.component.html (1 hunks)

Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

1 similar comment
Copy link

github-actions bot commented Oct 1, 2024

PR description must contain a link to a ClickUp (case-insensitive)

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: 3

🧹 Outside diff range and nitpick comments (4)
src/app/branding/c1-contents-config.ts (1)

187-187: Consider changing 'different than' to 'different from' for clarity

In standard English usage, 'different from' is preferred over 'different than' when making comparisons.

Apply this diff to improve the wording:

-connectorInfoLabel: 'Make sure you’re entering your integration credentials. These should be different than your Sage Intacct credentials.'
+connectorInfoLabel: 'Make sure you’re entering your integration credentials. These should be different from your Sage Intacct credentials.'
src/app/branding/fyle-contents-config.ts (3)

Line range hint 17-17: Change 'can not' to 'cannot' for correct usage

In the message, 'you can not change' should be 'you cannot change'.

Apply this diff to fix the grammatical error:

-subLabel: 'Expenses will be posted to the NetSuite Tenant Mapping selected here. Once configured, you can not change ' + brandingConfig.brandName + ' organization or Tenant Mapping.'
+subLabel: 'Expenses will be posted to the NetSuite Tenant Mapping selected here. Once configured, you cannot change ' + brandingConfig.brandName + ' organization or Tenant Mapping.'

Line range hint 179-179: Change 'can not' to 'cannot' for correct usage

In the message, 'you can not change' should be 'you cannot change'.

Apply this diff to fix the grammatical error:

-locationSubLabel: 'Expenses will be posted to the Sage Intacct Location entity selected here. Once configured, you can not change ' + brandingConfig.brandName + ' Organization or Location Entity.',
+locationSubLabel: 'Expenses will be posted to the Sage Intacct Location entity selected here. Once configured, you cannot change ' + brandingConfig.brandName + ' Organization or Location Entity.',

Line range hint 291-291: Add missing period after 'Sage Intacct' for proper punctuation

There is a missing period after 'Sage Intacct' in the sentence.

Apply this diff to fix the punctuation:

-customizeSectionSubLabel: 'In this section, you can customize the data that you\'d like to export from ' + brandingConfig.brandName + ' to Sage Intacct You can choose what data points need to be exported and what shouldn\'t be.'
+customizeSectionSubLabel: 'In this section, you can customize the data that you\'d like to export from ' + brandingConfig.brandName + ' to Sage Intacct. You can choose what data points need to be exported and what shouldn\'t be.'
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ac63bce and 79872c0.

📒 Files selected for processing (4)
  • src/app/branding/c1-contents-config.ts (1 hunks)
  • src/app/branding/fyle-contents-config.ts (1 hunks)
  • src/app/core/models/branding/content-configuration.model.ts (1 hunks)
  • src/app/shared/components/si/core/intacct-connector/intacct-connector.component.html (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/app/shared/components/si/core/intacct-connector/intacct-connector.component.html
🔇 Additional comments (1)
src/app/core/models/branding/content-configuration.model.ts (1)

182-183: Properties added align with existing naming conventions

The properties locationSubLabel and connectorInfoLabel are appropriately added to the connector configuration. They follow the existing structure and naming conventions, enhancing the configuration options for the Intacct connector.

@@ -183,7 +183,8 @@ export const c1Contents = {
connector: {
stepName: 'Connect to Sage Intacct',
subLabel: 'Provide your credentials to establish a secure connection between your Expense Management and Sage Intacct account. ',
locationSubLabel: 'Expenses will be posted to the Sage Intacct location entity selected here. You can\'t change the location entity once they\'re configured.'
locationSubLabel: 'Expenses will be posted to the Sage Intacct location entity selected here. You can\'t change the location entity once they\'re configured.',
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix pronoun agreement in 'locationSubLabel'

The term 'location entity' is singular, so the pronoun should be singular 'it' instead of 'they' in the sentence "You can't change the location entity once they're configured."

Apply this diff to correct the pronoun:

-locationSubLabel: 'Expenses will be posted to the Sage Intacct location entity selected here. You can\'t change the location entity once they\'re configured.',
+locationSubLabel: 'Expenses will be posted to the Sage Intacct location entity selected here. You can\'t change the location entity once it\'s configured.',
📝 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.

Suggested change
locationSubLabel: 'Expenses will be posted to the Sage Intacct location entity selected here. You can\'t change the location entity once they\'re configured.',
locationSubLabel: 'Expenses will be posted to the Sage Intacct location entity selected here. You can\'t change the location entity once it\'s configured.',

@@ -183,7 +183,8 @@ export const fyleContents = {
connector: {
stepName: 'Connect to Sage Intacct',
locationSubLabel: 'Expenses will be posted to the Sage Intacct Location entity selected here. Once configured, you can not change ' + brandingConfig.brandName + ' Organization or Location Entity.',
subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct account, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.'
subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct account, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.',
connectorInfoLabel: 'Please use the integration credentials you received via email. These are different from the ones you use to login to your Sage Intacct account.'
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Correct 'login' to 'log in' in the connectorInfoLabel

In the message, 'login' should be 'log in' when used as a verb.

Apply this diff to fix the grammatical error:

-connectorInfoLabel: 'Please use the integration credentials you received via email. These are different from the ones you use to login to your Sage Intacct account.'
+connectorInfoLabel: 'Please use the integration credentials you received via email. These are different from the ones you use to log in to your Sage Intacct account.'
📝 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.

Suggested change
connectorInfoLabel: 'Please use the integration credentials you received via email. These are different from the ones you use to login to your Sage Intacct account.'
connectorInfoLabel: 'Please use the integration credentials you received via email. These are different from the ones you use to log in to your Sage Intacct account.'

@@ -183,7 +183,8 @@
connector: {
stepName: 'Connect to Sage Intacct',
locationSubLabel: 'Expenses will be posted to the Sage Intacct Location entity selected here. Once configured, you can not change ' + brandingConfig.brandName + ' Organization or Location Entity.',
subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct account, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.'
subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct account, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.',
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Change 'account' to 'accounts' for grammatical correctness

In the text, 'To connect your Fyle and Sage Intacct account...', 'account' should be plural to match 'Fyle and Sage Intacct accounts'.

Apply this diff to fix the grammatical error:

-subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct account, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.',
+subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct accounts, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.',
📝 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.

Suggested change
subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct account, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.',
subLabel: 'To connect your ' + brandingConfig.brandName + ' and Sage Intacct accounts, follow the detailed instructions provided in the article to generate the credentials and establish a secure connection.',

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Extra Small PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants