René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Ability to use as standalone WP-CLI Package","articleBody":"This is the same request as I made a few years ago in #1, which at the time was closed because the official wp-cli \"package index\" wasn't accepting new submissions. Since then, they have [decided](https://make.wordpress.org/cli/2017/07/18/feature-development-discussion-recap/) to no longer maintain this separate index, and instead simply use any composer source, such as packagist, or a git repo directly.\r\n\r\nI've taken a few minutes to see what changes are needed, and it breaks down like this:\r\n\r\n1. Any check for `defined( 'ABSPATH' )` needs to be removed, or changed to check for `defined( 'WP_CLI' )` as an alternative\r\n2. `add_action` isn't available in the wp-cli bootstrap process, so `GF_CLI_Bootstrap::load_cli()` should be called unconditionally\r\n3. For the same reason, `GF_CLI_Bootstrap::load_addon()` needs to be loaded differently or conditionally\r\n4. Similarly, `plugin_dir_path()` isn't available during bootstrap, but is easily replaced with `dirname()` (and `rtrim()` to be really clean)\r\n\r\nWith these changes made, I can use the plugin as a global wp-cli package without any further issues. The only other small niggle is that the `type` in the composer.json file isn't `wp-cli-package` as [recommended](https://make.wordpress.org/cli/handbook/guides/commands-cookbook/#distribute-as-a-stand-alone-command), but this isn't a strict requirement.","author":{"url":"https://github.com/dotsam","@type":"Person","name":"dotsam"},"datePublished":"2022-02-09T22:15:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/39/gravityformscli/issues/39"}