[7.x] Only create the blueprints when not running on console #581
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.
We have our own package that uses the runway add-on. We have defined default Runway resources in this module. As we're updating our module to be compatible with the latest version of Runway we've come across a problem.
We want to define the blueprints in our module, thus we had the config file. In the latest Runway version, blueprints live in
.yaml
files under theresources/blueprints/vendor/runway
directory. We'd like to use thephp artisan vendor:publish
command to copy our module defined blueprints to the project. Sadly when runningphp artisan vendor:publish
the Runway service provider is registered first and creates empty blueprints. This causes the default blueprints to be already present, and thus can't ours be published.Our blueprint in the module:
brand.yaml
Blueprint after publishing (no error occured):
Let me know if you need any more information.