fix: include user-configured targets in unknown target validation#58
fix: include user-configured targets in unknown target validation#58runkids merged 2 commits intorunkids:mainfrom
Conversation
findUnknownSkillTargets only checked the built-in targets.yaml list, causing false warnings for custom targets defined in config.yaml. Pass configured target names from global/project config into the validation so user-defined targets are recognized.
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue where custom targets defined in a user's configuration were not being recognized during skill-level target validation, leading to incorrect warnings in the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly addresses the issue of false "unknown target" warnings by including user-configured targets during validation. The changes are well-implemented across the check and doctor commands, and the new unit test provides good coverage for the fix. I have one suggestion to improve code consistency by extracting a piece of logic into a new helper function, similar to what has been done for the global configuration.
|
Thanks for the contribution, @masonc15! Great fix. Will follow up with integration tests and minor refinements. |
…ct mode Follow-up to PR #58: check_project.go now extracts custom target names from project config and passes them to findUnknownSkillTargets, matching the global-mode fix. Also surfaces config load errors as warnings instead of silently ignoring them. Adds integration tests for check and doctor (global + project mode) verifying no false "unknown target" warnings.
Fixes #57
findUnknownSkillTargets()only checked the hardcodedtargets.yamllist when validating skill-leveltargetsfields. Custom targets defined in the user'sconfig.yamlwere not consulted, causing false "unknown target" warnings indoctorandcheck.Changes:
findUnknownSkillTargetsnow accepts anextraTargetNamesparameter with user-configured target namestargetNamesFromConfighelper extracts names from a global config's Targets mapdoctorandcheck(global and project) pass their configured targets through