-
Notifications
You must be signed in to change notification settings - Fork 13
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
Bug in "Parse contributors" #3
Comments
I noticed this bug too. It occurs every time a text line contains a colon ":" character. The code which performs this text replacement should be executed only for plugin header section and not in the whole document. Here's a quick fix: in wp_readme_to_markdow.js replace the line
with the following snippet
|
… if no section is found. Fixes unit tests: colons in main body of readme should not be treated as readme tags. Ref #3
Thanks @marcochiesi I've made some changes to your original PR, but this should be fixed now. I'll be publishing a new release shortly. |
There is a bug in the "Parse contributors" code...
I have a code block in my readme
header('Content-Type: application/xrd+xml; charset=' . get_bloginfo('charset'), true);
and the result is:
** header('Content-Type:** application/xrd+xml; charset=' . get_bloginfo('charset'), true);
The text was updated successfully, but these errors were encountered: