Skip to content

Conversation

jairmyree
Copy link
Member

@jairmyree jairmyree commented Jul 22, 2025

Currently the script does not properly escape "&" when creating the readme html. This leads to the Javadoc compiler believing it is a malformed html tag.

This PR fixes the aforementioned issue.

@Copilot Copilot AI review requested due to automatic review settings July 22, 2025 17:51
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes a critical issue where the ampersand character (&) was not being properly encoded as & in HTML generated from README files, causing Javadoc compilation failures due to malformed HTML tags.

Key Changes

  • Added HTML entity encoding for ampersand characters before processing README content
  • Inserted the encoding step before the existing code snippet tag cleaning process
  • Modified the downstream processing to use the escaped content
Comments suppressed due to low confidence (1)

eng/pipelines/scripts/generate_overview_from_readme.py:48

  • [nitpick] The variable name 'escaped_readme_content_lines' could be more specific. Consider 'html_escaped_readme_content_lines' to clarify that this is HTML escaping, not general escaping.
        escaped_readme_content_lines = []

@jairmyree jairmyree changed the title Fix failure to properly encode & Fix failure to properly escape & Jul 22, 2025
@jairmyree
Copy link
Member Author

@alzimmermsft For the sake of time, I'm going to use this version of the PR to due this month's release of patches, and then I'll circle back to update with your suggestion.

@jairmyree jairmyree merged commit 208c264 into Azure:main Jul 28, 2025
11 checks passed
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.

3 participants