Skip to content

fix: Ensure __parse_tool returns correct used_auth_keys #204

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

Merged
merged 3 commits into from
May 12, 2025

Conversation

anubhav756
Copy link
Contributor

This PR refactors __parse_tool to accurately determine and return the used_auth_keys value.

Investigation revealed that the previously incorrect value was not referenced elsewhere, meaning this bug did not manifest as an active issue. However, this correction enhances the reliability of __parse_tool for any future use cases.

Note

Unit tests for the underlying helper function that identifies these used auth keys, including tests for the correct values, had already been added in #203. As this PR's change corrects a value that wasn't actively tested or used, no unit test modifications are needed here.

@anubhav756 anubhav756 self-assigned this May 1, 2025
@anubhav756 anubhav756 requested a review from a team as a code owner May 1, 2025 04:18
@anubhav756 anubhav756 force-pushed the anubhav-used-params branch from 4995d2f to 8b5e777 Compare May 2, 2025 13:34
@anubhav756 anubhav756 force-pushed the anubhav-fix-used-params branch from e5763b9 to be9ec4b Compare May 2, 2025 13:34
@anubhav756 anubhav756 force-pushed the anubhav-used-params branch from 8b5e777 to ef02615 Compare May 5, 2025 08:25
@anubhav756 anubhav756 force-pushed the anubhav-fix-used-params branch from be9ec4b to 2e36f66 Compare May 5, 2025 08:25
@anubhav756 anubhav756 force-pushed the anubhav-used-params branch from ef02615 to 684f744 Compare May 5, 2025 14:19
@anubhav756 anubhav756 force-pushed the anubhav-fix-used-params branch from 2e36f66 to ea1a66b Compare May 5, 2025 14:19
@anubhav756 anubhav756 force-pushed the anubhav-used-params branch from 684f744 to e96a22f Compare May 12, 2025 12:01
@anubhav756 anubhav756 force-pushed the anubhav-fix-used-params branch from ea1a66b to f3e7df1 Compare May 12, 2025 12:01
@anubhav756 anubhav756 force-pushed the anubhav-used-params branch from e96a22f to 4738f4d Compare May 12, 2025 12:29
@anubhav756 anubhav756 force-pushed the anubhav-fix-used-params branch from f3e7df1 to f56cc68 Compare May 12, 2025 12:30
Base automatically changed from anubhav-used-params to main May 12, 2025 12:32
We will remove this once we actually implement the `strict` flag and centralize this functionality by moving this check to the tool's constructor in a future PR.
@anubhav756 anubhav756 force-pushed the anubhav-fix-used-params branch from f56cc68 to 6ff0142 Compare May 12, 2025 12:34
@anubhav756 anubhav756 merged commit d0b5020 into main May 12, 2025
19 checks passed
@anubhav756 anubhav756 deleted the anubhav-fix-used-params branch May 12, 2025 13:04
@release-please release-please bot mentioned this pull request May 12, 2025
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.

2 participants