Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make configs and translations publishable #2182

Merged
merged 7 commits into from Aug 18, 2020
Merged

Make configs and translations publishable #2182

merged 7 commits into from Aug 18, 2020

Conversation

aerni
Copy link
Contributor

@aerni aerni commented Aug 6, 2020

I had to open a new PR because I had to change the target branch. This is the same PR as #2135.

Summary

An addon's config and translations now automatically merge and load.

You can also publish the files:

// Config
vendor:publish --tag="addon-slug-config"

// Translations
vendor:publish --tag="addon-slug-translations"

If you don't want to merge the config and load the translations you can opt-out of it by setting the following properties in the addon's Service Provider:

protected $config = false;
protected $translations = false;

There was an error when your addon didn't have a config or translations. If you don't need any, you now don't have to manually set `protected $config = false` and `protected $translations = false` anymore.
@jasonvarga jasonvarga merged commit a125700 into statamic:master Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants