Skip to content

Conversation

@alt-glitch
Copy link
Contributor

No description provided.

@entelligence-ai-pr-reviews
Copy link

⚠️ Trial Period Expired ⚠️

Your trial period has expired. To continue using this feature, please upgrade to a paid plan. You can upgrade your account here - https://entelligence.ai/manage/billing

@vercel
Copy link

vercel bot commented Mar 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
composio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 27, 2025 10:41am

"GOOGLEADS_AUTH",
"NO_AUTH",
"CALCOM_AUTH",
"BILLCOM_AUTH"

Choose a reason for hiding this comment

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

Consider adding a brief comment explaining what BILLCOM_AUTH is and its use case. This will help future maintainers understand the purpose of this authentication scheme.

"GOOGLEADS_AUTH",
"NO_AUTH",
"CALCOM_AUTH",
"BILLCOM_AUTH"

Choose a reason for hiding this comment

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

Consider adding BILLCOM_AUTH to the docstring of AuthSchemeType to maintain consistency with other auth schemes in the type definition.

@github-actions
Copy link
Contributor

This comment was generated by github-actions[bot]!

JS SDK Coverage Report

📊 Coverage report for JS SDK can be found at the following URL:
https://pub-92e668239ab84bfd80ee07d61e9d2f40.r2.dev/coverage-14104592047/coverage/index.html

📁 Test report folder can be found at the following URL:
https://pub-92e668239ab84bfd80ee07d61e9d2f40.r2.dev/html-report-14104592047/html-report/report.html

@shreysingla-bot
Copy link

Code Review Summary

Changes Overview

  • Added BILLCOM_AUTH authentication scheme to both JavaScript and Python SDKs
  • Changes are consistent across all relevant type definitions and schemas
  • Implementation follows existing patterns for auth scheme integration

Suggestions

  1. Documentation:
    • Add brief comments explaining BILLCOM_AUTH's purpose and use case
    • Consider updating type definition docstrings

Code Quality: ✅ Good

  • Changes are minimal and focused
  • Maintains type safety across both language implementations
  • Follows existing code patterns and structure
  • No apparent bugs or issues

Testing Considerations

  • Consider adding test cases for the new auth scheme
  • Verify integration with Bill.com authentication flow

Overall, the changes look clean and well-structured. Main suggestion is to improve documentation for future maintainability.

@angrybayblade
Copy link
Contributor

marking stale

@CryogenicPlanet CryogenicPlanet deleted the sid/fix-bill-auth-scheme branch October 28, 2025 02:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants