[5.5] Add prompt to vendor:publish to specify which provider/tag to publish

[fitztrev]

By default, artisan vendor:publish will publish everything it can find. Passing the --provider flag is the way around this but you have to lookup the package's service provider class name along with its namespace (long and inconsistent naming across packages).

This pull request adds a prompt to allow the user to specify the package for which they want to publish files.

Prompt can be avoided by using the --all flag or by continuing to pass a --provider.

Edit: Updated screen capture gif below

[browner12]

could you make option 0 publish everything? that way people wouldn't have to remember the flag?

this is awesome, BTW.

[edenreich]

Very cool feature, I think its very useful, good job!

[MarkVaughn]

This might work

        $choice = $this->choice(
            "Which package's files would you like to publish?",
            array_merge(
                ['All'],
                ServiceProvider::providersAvailableToPublish()
            ),
            0
        );
        
        return $choice === 'All' ? null : $choice;

[antonkomarev]

Is there is a way to skip command prompt? It will be useful for deploy automation tools.

[browner12]

you can still use the --provider flag if you'd like to use it with automation

[antonkomarev]

@browner12 thanks! Don't know why I've missed that from first comment.

[fitztrev]

Thanks for the feedback. I prepended the 0 option to publish all.

[bbashy]

Great stuff!

[taylorotwell]

Does this also show available tags?

[fitztrev]

Publishable tags have now been added as choices in the prompt. Gif has been updated to show what it looks like.

[browner12]

this update seems a little strange to me. aren't tags a subset of a provider?

Wouldn't you first select a provider, and then (if it has them) select the tag after that?

Is it possible to do a two step choice like this with the command?

[fitztrev]

Tags are a subset but they can be shared across multiple packages. So this lets you publish all the config or migrations-tagged files for all providers at once.

I'm OK with this functionality. If someone wants to publish only the views for a specific provider that also has config or migrations, they still can use --provider="xyz" --tag=views in conjunction with each other.

[taylorotwell]

Nice addition @fitztrev!

[jbrooksuk]

This is awesome!

[mitoop]

What i want! Awesome!

[juniorb2ss]

@fitztrev Maybe functionality to publish specific tags and providers like: 4,2,8 in same time.

[fitztrev]

@juniorb2ss it's just an interface on top of the --provider and --tags options that were already part of the command. You can't pass multiple --providers. and if you try to do both a provider and a tag, it treats it like an AND. So it would likely be confusing. Not worth it IMO.