Skip to content

Fixed pipe character breaking markdown table rendering in README#97

Merged
drkrillo merged 1 commit into
drkrillo:mainfrom
Prerana-Sodankoor:fix/pipe-character-markdown-table
May 27, 2026
Merged

Fixed pipe character breaking markdown table rendering in README#97
drkrillo merged 1 commit into
drkrillo:mainfrom
Prerana-Sodankoor:fix/pipe-character-markdown-table

Conversation

@Prerana-Sodankoor
Copy link
Copy Markdown

Fixes #91

I ran the project locally using pytorch as the username and reproduced the issue. Some issue titles contain pipe characters (|), for example: [MX | Triton] Create MX matmul op using new scaled_dot op in Triton.Since | is interpreted as a column separator in markdown tables, it caused rows in the generated README table to render incorrectly.This PR fixes the issue by escaping pipe characters in issue titles inside render_template() in app/core/api_handler.py before rendering the markdown table.

Copy link
Copy Markdown
Owner

@drkrillo drkrillo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR looks great.

Thanks for the context in the PR description.

Hope to see you around contributing again! :)

I hope the Issue was useful, and let me know if I cna help you with anything.

Comment thread app/core/api_handler.py
'repo': row['repo'],
'language': row['language'],
'title': row['title'],
'title': row['title'].replace('|', '\\|'), # Escape '|' to avoid breaking markdown table rows
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the fact that you are scaping the | instead of replacing it with another character. Nice move!

@drkrillo drkrillo merged commit f65b74c into drkrillo:main May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: Incorrect parsing of some issues

3 participants