-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: Fix main file as #1116
fix: Fix main file as #1116
Conversation
WalkthroughThe changes in this pull request involve a correction to the HTML template of the Changes
Possibly related PRs
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
src/app/branding/fyle-contents-config.ts (1)
253-253
: Consider using template literals for better readabilityWhile the string concatenation works, template literals would make the code more readable and maintainable.
- customizeSectionSubLabel: 'In this section, you can customize the data that you\'d like to export from ' + brandingConfig.brandName + ' to Xero. 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 Xero. You can choose what data points need to be exported and what shouldn't be.`,
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 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/integrations/xero/xero-shared/xero-advanced-settings/xero-advanced-settings.component.html
(1 hunks)
🔇 Additional comments (4)
src/app/integrations/xero/xero-shared/xero-advanced-settings/xero-advanced-settings.component.html (2)
106-106
: LGTM: Dynamic binding for customization section sub-label
The change improves maintainability by using dynamic content from brandingContent instead of hardcoded text.
114-115
: LGTM: Dynamic bindings for memo structure field labels
The changes enhance maintainability and localization support by using dynamic content from brandingContent for both label and sub-label.
src/app/core/models/branding/content-configuration.model.ts (1)
251-253
: LGTM: Type definitions for new branding content properties
The added type definitions provide proper type safety for the new branding content properties and follow consistent naming patterns.
src/app/branding/c1-contents-config.ts (1)
257-260
: LGTM: Clear and consistent branding content
The added content provides clear guidance to users while maintaining a consistent messaging style across the application.
@@ -250,6 +250,7 @@ export const fyleContents = { | |||
topLevelMemoStructureSubLabel: 'Select the datapoints you\'d like to export to Xero’s top-level memo field when exporting expenses from Fyle.', | |||
memoStructureLabel: 'Customize the Line-Item Level Memo Field', | |||
memoStructureSubLabel: 'Select the datapoints you\'d like to export to Xero\’s line-item level memo field when exporting expenses from Fyle.', | |||
customizeSectionSubLabel: 'In this section, you can customize the data that you\'d like to export from ' + brandingConfig.brandName + ' to Xero. You can choose what data points need to be exported and what shouldn\'t be.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Inconsistency found in customization section labels across integrations
The search results reveal variations in the customization labels:
- Fyle-Xero and Fyle-Sage Intacct use the longer format: "In this section, you can customize the data that you'd like to export from [brandName] to [Integration]. You can choose what data points need to be exported and what shouldn't be."
- QuickBooks Desktop uses a similar longer format
- Other Xero and Sage Intacct configurations use a shorter format: "Customize the data that you'd like to export from Expense Management to [Integration] by choosing which data points need to be exported."
🔗 Analysis chain
Verify consistency of customization labels across integrations
The customization label is consistent with other integration sections (NetSuite, Intacct), which is good for maintaining a uniform user experience.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify consistency of customization labels across all integration sections
# Test: Search for customizeSectionSubLabel in all integration sections
rg "customizeSectionSubLabel.*export.*data" -A 1 -B 1
Length of output: 2656
4c70551
to
b8ff308
Compare
PR title must start with "fix:", "feat:", "chore:", "refactor", or "test:" (case-insensitive) |
|
* fix: remove validation temporarily (#1111) * fix: add a default bank account field for CCC expenses * fix: add missing options to bank accounts on page init * fix: dynamic content for xero customize settings (#1112) * fix: update sublabel key to avoid build fail (#1116) * fix: Prod fixes of QBD direct (#1118) * fix bugs (#1119) * refactor: capitalization * fix: only ccc exports not being saved (#1121) --------- Co-authored-by: Ashwin Thanaraj <[email protected]> Co-authored-by: Nilesh Pant <[email protected]> Co-authored-by: Dhaarani <[email protected]> Co-authored-by: Anish Kr Singh <[email protected]>
* fix: restrict JE modules to group by expense only * fix: add a default bank account field for CCC expenses (#1114) * fix: remove validation temporarily (#1111) * fix: add a default bank account field for CCC expenses * fix: add missing options to bank accounts on page init * fix: dynamic content for xero customize settings (#1112) * fix: update sublabel key to avoid build fail (#1116) * fix: Prod fixes of QBD direct (#1118) * fix bugs (#1119) * refactor: capitalization * fix: only ccc exports not being saved (#1121) --------- Co-authored-by: Ashwin Thanaraj <[email protected]> Co-authored-by: Nilesh Pant <[email protected]> Co-authored-by: Dhaarani <[email protected]> Co-authored-by: Anish Kr Singh <[email protected]> --------- Co-authored-by: Ashwin Thanaraj <[email protected]> Co-authored-by: Nilesh Pant <[email protected]> Co-authored-by: Dhaarani <[email protected]> Co-authored-by: Anish Kr Singh <[email protected]>
* fix: initialize chart of accounts multiselect when there is no api response (#1110) * fix: remove the posted at date option for ccc expenses grouped by report (#1105) * fix: update login error flow and fix redirect url (#1117) * fix: restrict JE modules to group by expense only (#1113) * fix: restrict JE modules to group by expense only * fix: add a default bank account field for CCC expenses (#1114) * fix: remove validation temporarily (#1111) * fix: add a default bank account field for CCC expenses * fix: add missing options to bank accounts on page init * fix: dynamic content for xero customize settings (#1112) * fix: update sublabel key to avoid build fail (#1116) * fix: Prod fixes of QBD direct (#1118) * fix bugs (#1119) * refactor: capitalization * fix: only ccc exports not being saved (#1121) --------- Co-authored-by: Ashwin Thanaraj <[email protected]> Co-authored-by: Nilesh Pant <[email protected]> Co-authored-by: Dhaarani <[email protected]> Co-authored-by: Anish Kr Singh <[email protected]> --------- Co-authored-by: Ashwin Thanaraj <[email protected]> Co-authored-by: Nilesh Pant <[email protected]> Co-authored-by: Dhaarani <[email protected]> Co-authored-by: Anish Kr Singh <[email protected]> --------- Co-authored-by: Ashwin Thanaraj <[email protected]> Co-authored-by: Nilesh Pant <[email protected]> Co-authored-by: Dhaarani <[email protected]> Co-authored-by: Anish Kr Singh <[email protected]>
Description
Please add PR description here, add screenshots if needed
Clickup
https://app.clickup.com/t/
Summary by CodeRabbit