Conversation
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 standardizes the build output format by introducing a configurable policy to control the display of target names. It refactors how build progress messages are generated, ensuring that target names are consistently included when the policy is enabled, and removes duplicate namespace information for a cleaner, more uniform user experience. 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
|
f803ae1 to
5cf3f01
Compare
There was a problem hiding this comment.
Code Review
This pull request introduces a significant and valuable refactoring to unify the build output, making it more consistent across different rules. A new policy build.show_target is added to control the display of target names, which is a great feature for improving build log clarity. The changes are extensive, touching many rule files to adopt the new centralized progress reporting mechanism. While the overall implementation is solid, I've identified a critical bug in the new apply_target helper function that could lead to a runtime error, and a minor formatting issue in the swift rule that results in duplicated output. Addressing these will make this PR ready for merging.
5cf3f01 to
8779eaf
Compare
|
This patch has made too many changes, and I can't review it quickly right now. If it's just about adding targets to the progress bar, some refactoring is needed, and the current patch isn't sufficient. I'll take a look at it when I have time. |
|
try this patch, #7364 we need not to modify so many files |
|
done |
it's perfect |
This PR is a proposition of uniformize all rules build outputs
it add a policy (enabled by default) "build.show_target" which control if target name is printed when compiling/generating/preprocessing/etc... in a rule
it also remove the namespace print from some progress.show as this information is already contained in the target:fullname() string
i don't know if the policy should be true by default, it can be a breaking change for tools that parse xmake output
and maybe add a way to configure if the namespace is showed along side the target name ?
before:
after (policy enabled, the default in this PR):
after (policy disabled):