Add separate method for customer expected fields

[angrybayblade]

Important

Add get_expected_params_for_user() and rename get_expected_params() to get_auth_scheme_for_app() in ComposioToolSet.

• Methods:
  • Add get_expected_params_for_user() to ComposioToolSet for retrieving expected fields for a user.
  • Rename get_expected_params() to get_auth_scheme_for_app() in ComposioToolSet for clarity.
• Imports:
  • Remove unused import AuthSchemeField from toolset.py.

^{This description was created by for 7d3de10. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 7d3de10 in 13 seconds

More details

• Looked at 69 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. python/composio/tools/toolset.py:1042

• Draft comment:
  Consider providing more guidance in the error message on how to obtain the integration ID if it's not available.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The method get_expected_params_for_user is added to retrieve expected input fields for a user based on integration ID or app. The logic seems correct, but there is a potential issue with the error message in the exception handling block. The message suggests creating an integration, but it might be more helpful to provide guidance on how to obtain the integration ID if it's not available.

Workflow ID: wflow_HMrDWFrP5Az8sV6Z

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[github-actions]

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-11381070999/coverage/index.html

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