Add PucReadmeParser class for parsing plugin readme files#8
Merged
Conversation
- Introduced a new class `PucReadmeParser` to handle the parsing of WordPress plugin readme files. - The parser supports Markdown transformations and extracts essential metadata such as plugin name, required PHP version, stable tag, tags, contributors, and various sections (description, installation, FAQ, etc.). - Implemented methods for sanitizing text, filtering content, and handling code blocks. - The class utilizes Parsedown for Markdown parsing and ensures compatibility with WordPress standards.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently tha
646D
n what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several post-release refinements to the Redis Queue plugin's 2.0.0 admin interface, focusing on improved user experience, more robust asset loading, and minor internal housekeeping. The most significant changes include a new noscript warning for users without JavaScript, enhanced feedback during test job submission, and a switch to more reliable asset URLs. These updates are non-breaking and address edge cases and usability issues reported after the initial release.
User Experience Improvements
Asset Loading Reliability
../../assets/...URLs toplugins_url(), making asset paths more robust against path traversal issues and CDN rewriting. Also added an inline preload marker for easier debugging of asset loading failures. [1] [2]Bug Fixes
Internal Housekeeping
These changes are documented in both the changelog and readme for transparency and easier migration.