fix : pr type rendering with markers

[benedict-lee]

User description

Improvement to change the output format of a list object to a comma-separated string for PR type

---

PR Type

Bug fix, Enhancement

---

Description

• Fixed rendering of PR types with markers.

• Enhanced handling of ai_type as a list or string.

• Improved formatting to output comma-separated PR types.

---

Changes walkthrough 📝

	Relevant files
Enhancement	pr_description.py Fix and enhance PR type rendering logic                                    pr_agent/tools/pr_description.py Fixed issue with ai_type rendering in PR body. Added handling for ai_type as a list to generate comma-separated types. Ensured backward compatibility for ai_type as a string. +5/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Variable Usage The pr_type variable is used before being defined in the case where ai_type is not a list. Consider moving the body.replace() call after all pr_type assignments. body = body.replace('pr_agent:type', pr_type)

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Sanitize user-provided content to prevent potential security vulnerabilities Sanitize the PR type strings before joining them to prevent potential XSS or injection issues, as the values might come from external sources. pr_agent/tools/pr_description.py [484-485] -pr_types = [f"{ai_header}{t}" for t in ai_type] +pr_types = [f"{ai_header}{html.escape(str(t))}" for t in ai_type] pr_type = ','.join(pr_types) Apply this suggestion Suggestion importance[1-10]: 8 Why: This is an important security enhancement as it prevents potential XSS attacks by sanitizing user-provided content before it's included in the PR description.	8
General	Add validation to ensure string replacement operation has the expected target Add error handling for the case when body doesn't contain the 'pr_agent:type' marker, as the replace operation would silently fail and potentially cause confusion. pr_agent/tools/pr_description.py [488] -body = body.replace('pr_agent:type', pr_type) +if 'pr_agent:type' in body: + body = body.replace('pr_agent:type', pr_type) +else: + get_logger().warning(f"Marker 'pr_agent:type' not found in PR body for {self.pr_id}") Apply this suggestion Suggestion importance[1-10]: 5 Why: Adding explicit validation for marker presence would improve error handling and debugging, though the current silent failure isn't critical since the regex check already prevents most issues.	5

• Author self-review: I have reviewed the PR code suggestions, and addressed the relevant ones.