fix: resolve markdown index out of range issue when parsing inline code

[weirui-kong]

#55 一种可能的修复方法

[gemini-code-assist]

Summary of Changes

Hello @weirui-kong, 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!

此拉取请求旨在通过引入必要的边界检查来增强 Markdown 内联代码解析的健壮性。它解决了在处理内联代码时可能发生的潜在索引越界错误，确保在为代码字符串添加格式属性时，操作始终在有效范围内进行，从而提高了应用程序的稳定性和可靠性。

Highlights

• 修复范围越界问题: 解决了在解析 Markdown 内联代码时可能出现的索引越界问题。
• 增加安全检查: 在为内联代码添加属性之前，引入了对缓冲区长度和代码字符串长度的有效性检查，以防止运行时错误。
• 优化属性应用: 确保了在 AMAttributedStringRenderer.m 中，为内联代码的起始和结束空格应用 NSKernAttributeName 和 NSFontAttributeName 时，范围始终有效。

🧠 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.

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 introduces a fix for a potential 'index out of range' crash when parsing inline code. It adds a defensive check to ensure the buffer length is sufficient before attempting to add attributes. The fix is correct and effectively prevents the crash. I've included one minor suggestion to simplify the conditional check for better code clarity.

[gemini-code-assist]

The codeLength >= 2 check is redundant. The codeStr is created by wrapping the input code with two \u00A0 characters, so its length is guaranteed to be at least 2. This check can be safely removed to simplify the condition.

Suggested change

	if (self.buffer && currentLength >= codeLength && codeLength >= 2) {
	if (self.buffer && currentLength >= codeLength) {