Skip to content

fix: handle parentheses in URL content - #25

Merged
xHeaven merged 8 commits into
mainfrom
fix-parenthesis-content
Sep 4, 2026
Merged

fix: handle parentheses in URL content#25
xHeaven merged 8 commits into
mainfrom
fix-parenthesis-content

Conversation

@aidan-casey

Copy link
Copy Markdown
Member

No description provided.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

Benchmark Results

Comparison of fix-parenthesis-content against main (98507e12095acdd8ef4df53de13e9eaabdc47f94).

Open to see the benchmark results

No benchmark changes above ±5%.

Generated by phpbench against commit 1f25464

@aidan-casey

Copy link
Copy Markdown
Member Author

This PR fixes links with parenthesis present in the URI. It supports ending parenthesis when they have a start parenthesis in the content and when they are escaped. I am guessing this is consistent with GitHub and will test below.

Start and End Parenthesis
.NET best practices

End Parenthesis Only
.NET best practices?redirectedfrom=MSDN)

Escaped End Parenthesis Only
.NET best practices

@aidan-casey
aidan-casey requested a review from xHeaven September 4, 2026 21:47
@xHeaven
xHeaven merged commit 99871ca into main Sep 4, 2026
4 checks passed
@xHeaven
xHeaven deleted the fix-parenthesis-content branch September 4, 2026 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants