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

Provide a BC layer for files in "app/config/" referenced by PluginSkeleton #9672

Merged
merged 1 commit into from
Aug 26, 2018

Conversation

pamil
Copy link
Contributor

@pamil pamil commented Aug 24, 2018

Files app/config/routing.yml, app/config/routing_dev.yml and app/config/security.yml are referenced in PluginSkeleton. This PR provides a backwards compatibility layer for them.

@pamil pamil added Potential Bug Potential bugs or bugfixes, that needs to be reproduced. Maintenance CI configurations, READMEs, releases, etc. labels Aug 24, 2018
@pamil pamil added this to the v1.3.0 milestone Aug 24, 2018
@@ -1,24 +0,0 @@
# This file is auto-generated during the composer install
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is not referenced by neither Sylius-Standard nor PluginSkeleton.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, we still need it here, it is being removed in #9665.


declare(strict_types=1);

@trigger_error('Importing files from Sylius/Sylius\'s "app/config" directory is deprecated since Sylius 1.3.', \E_USER_DEPRECATED);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deprecating YAML files is kinda weird 🎉

@pamil pamil force-pushed the config-files-bc-layer branch from 500fd62 to 96bbbc9 Compare August 24, 2018 15:16
@teohhanhui
Copy link
Contributor

teohhanhui commented Aug 24, 2018

I think this is exactly why these files should be removed from Sylius/Sylius altogether. They should only be kept for BC. But moving forward, application-related configuration must not be in Sylius/Sylius.

teohhanhui referenced this pull request in Brille24/SyliusTierpricePlugin Aug 24, 2018
@lchrusciel lchrusciel merged commit 1b8cc75 into Sylius:master Aug 26, 2018
@lchrusciel
Copy link
Member

Thanks Kamil!

@pamil pamil deleted the config-files-bc-layer branch August 27, 2018 08:32
@pamil
Copy link
Contributor Author

pamil commented Aug 27, 2018

@teohhanhui I'm trying to solve that by making Sylius-Standard a part of Sylius/Sylius (which is subtree split back into Sylius-Standard). This way we can run tests on this repo while having one less place with configuration.

@teohhanhui
Copy link
Contributor

Yes, make them part of the application, not part of Sylius. Sylius-Standard should be treated purely as a distribution, aka recommended scaffolding / project template. No BC guarantees.

@pamil pamil mentioned this pull request Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance CI configurations, READMEs, releases, etc. Potential Bug Potential bugs or bugfixes, that needs to be reproduced.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants