issue-66: Support registering assets to the wp dependency registry #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renatonascalves
changed the title
mogmarsh
approved these changes
Jan 16, 2025
Comment on lines
+436
to
+438
| } elseif ( version_compare( $GLOBALS['wp_version'], '6.3', '<' ) ) { | ||
| // If this is for a script, pass the in_footer argument when on a version prior to 6.3. | ||
| $enqueue_options = $args['in_footer']; |
There was a problem hiding this comment.
do we even want to support < 6.3 anymore? It came out over 17 months ago
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #66
This PR adds support for registering assets to the WordPress dependency registry as part of the efforts to enhance the query monitor functionality. Additionally, it includes unit tests to ensure the reliability of this new feature.