Fix attribute name case for CodeChange

[nighca]

Fix attribute parsing failure for <code-change> in Copilot output.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 a critical parsing issue within the Copilot output by standardizing an attribute name. The change ensures that the <code-change> custom element correctly interprets its remove-line-count attribute, thereby preventing errors and improving the reliability of code change displays.

Highlights

• Attribute Name Correction: Corrected the attribute name removeLineCount to remove-line-count within the CodeChange.vue component's attribute schema to resolve parsing failures in Copilot output.

🧠 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

• spx-gui/src/components/copilot/custom-elements/CodeChange.vue
  • Renamed the removeLineCount attribute to remove-line-count in the attributes schema.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly changes the attribute name in the Zod schema from camelCase (removeLineCount) to kebab-case (remove-line-count) to fix a parsing issue with the <code-change> custom element. The change is appropriate as HTML attributes are typically in kebab-case. I've added a suggestion to further improve the schema's robustness by adding validation for the numeric string format.

[Copilot]

Pull request overview

This PR fixes a Copilot custom element attribute mismatch by updating the <code-change> attributes schema to use kebab-case, aligning the prompt/schema with how markdown/HTML attributes are parsed and sanitized in the UI renderer.

Changes:

• Update CodeChange custom element attribute schema key from removeLineCount to remove-line-count to match expected HTML attribute naming.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[fennoai]

Clean, minimal, and correct fix. The detailedDescription example already used remove-line-count (kebab-case), but the attributes schema was inconsistent — this aligns them. The full pipeline (HAST parsing → sanitize → Vue prop delivery) continues to work correctly since getComponentPropNames reads camelCase removeLineCount from defineProps and converts it to remove-line-count for the sanitize allowlist.

One suggestion: a regression test covering the attribute name round-trip through the parsing pipeline would catch similar mismatches early.