feat: allow non-standard namespace for SoloServiceProvider #14
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.
If your
SoloServiceProvider
is stored in a namespace which is not the standardApp\Providers
, Laravel Solo is gonna "complain" because commands are being registered from an unsafe location.This PR adds the method
useCustomNamespaceProvider
, which tells Laravel Solo to consider it as a safe location to register commands from.This method takes the service provider instance itself as an argument of
AaronFrancis\Solo\Providers\SoloApplicationServiceProvider
type (which your service provider is subclass of): this ensures that the user is not trying to register as safe an arbitrary class namespace.Example: