Skip to content

Escaped : in .properties causes invalid URLs in generated .yaml #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SableRaf opened this issue May 16, 2025 · 0 comments · Fixed by #77
Closed

Escaped : in .properties causes invalid URLs in generated .yaml #76

SableRaf opened this issue May 16, 2025 · 0 comments · Fixed by #77
Assignees
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@SableRaf
Copy link
Contributor

SableRaf commented May 16, 2025

Description

The Gradle task writeLibraryProperties (in processing-library-template) correctly escapes : in .properties files (e.g. https\://...) per the file format spec. However, the parse_and_validate_properties_txt.py script in this repository does not unescape these values before writing them to .yaml.

As a result, URLs appear broken in the Contribution Manager.

Expected behavior

Escape sequences like \: should be unescaped when converting .properties to .yaml.

Suggested fix

Update the parse_text() function to unescape escaped characters such as \: before validation and output.

Related to prior conversation in processing/processing-library-template#88

@SableRaf SableRaf added bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed labels May 16, 2025
@mingness mingness self-assigned this May 16, 2025
@mingness mingness linked a pull request May 16, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants