-
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
xero c1 error fix #959
xero c1 error fix #959
Conversation
WalkthroughThe changes involve updates to the Changes
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 (
|
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: 2
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- src/app/shared/components/configuration/configuration-import-field/configuration-import-field.component.ts (3 hunks)
Additional context used
GitHub Check: lint
src/app/shared/components/configuration/configuration-import-field/configuration-import-field.component.ts
[failure] 218-218:
Unexpected console statement
[failure] 218-218:
Missing semicolon
[failure] 280-280:
Unexpected console statement
[failure] 280-280:
Missing semicolon
Additional comments not posted (1)
src/app/shared/components/configuration/configuration-import-field/configuration-import-field.component.ts (1)
313-313
: LGTM!The updated condition for disabling the
dependentFieldImportToggle
control looks good. It ensures that the control is only disabled when it has a truthy value.
@@ -276,6 +277,7 @@ | |||
|
|||
disableDestinationFields() { | |||
this.expenseFieldsGetter.controls.forEach((expenseField) => { | |||
console.log(expenseField) |
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.
Remove the console.log
statement.
The console.log
statement should be removed before merging to production. If it was added for debugging, consider using a debugger instead.
Also, add a semicolon at the end of the statement to adhere to the code style.
- console.log(expenseField)
+ console.log(expenseField);
Committable suggestion was skipped due to low confidence.
Tools
GitHub Check: lint
[failure] 280-280:
Unexpected console statement
[failure] 280-280:
Missing semicolon
console.log("Op", expenseField) | ||
if (expenseField.get('destination_field')?.value === 'CUSTOMER' && this.appName === AppName.XERO) { |
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.
Remove the console.log
statement.
The console.log
statement should be removed before merging to production. If it was added for debugging, consider using a debugger instead.
Also, add a semicolon at the end of the statement to adhere to the code style.
- console.log("Op", expenseField)
+ console.log("Op", expenseField);
Committable suggestion was skipped due to low confidence.
Tools
GitHub Check: lint
[failure] 218-218:
Unexpected console statement
[failure] 218-218:
Missing semicolon
Summary by CodeRabbit
expenseField
before disabling destination fields, aiding in debugging and user experience.