Excluding Data Fixtures for being autloaded by composer in a Symfony 3.4 application
I am using doctrine/data-fixtures
in dev environments and require it as follows:
composer.json:
"autoload": {
"psr-0": {
"": "src/",
"SymfonyStandard": "app/"
},
"classmap": [ "app/AppKernel.php", "app/AppCache.php" ]
},
"require-dev": {
"symfony/maker-bundle": "^1.8",
"phpunit/phpunit": "^7.0",
"doctrine/data-fixtures": "dev-rfc1872 as v1.2.1",
"doctrine/doctrine-fixtures-bundle": "^3.0"
},
In my Symfony 3.4 application my data fixtures live in /src/AppBundle/DataFixtures/ORM/*.php
.
When I run composer, which in turn runs a Symfony cache:clear I get the following error:
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'"
command:
In DefinitionErrorExceptionPass.php line 37:
While discovering services from namespace "AppBundle", an error was thrown
when processing the class "AppBundleDataFixturesORMLoadCourseData": "Cl
ass DoctrineCommonDataFixturesAbstractFixture not found".
I would like to exclude the DataFixtures namespace from being autoloaded but I cannot find a way to do that.
php symfony composer-php symfony3.4 autoloader
add a comment |
I am using doctrine/data-fixtures
in dev environments and require it as follows:
composer.json:
"autoload": {
"psr-0": {
"": "src/",
"SymfonyStandard": "app/"
},
"classmap": [ "app/AppKernel.php", "app/AppCache.php" ]
},
"require-dev": {
"symfony/maker-bundle": "^1.8",
"phpunit/phpunit": "^7.0",
"doctrine/data-fixtures": "dev-rfc1872 as v1.2.1",
"doctrine/doctrine-fixtures-bundle": "^3.0"
},
In my Symfony 3.4 application my data fixtures live in /src/AppBundle/DataFixtures/ORM/*.php
.
When I run composer, which in turn runs a Symfony cache:clear I get the following error:
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'"
command:
In DefinitionErrorExceptionPass.php line 37:
While discovering services from namespace "AppBundle", an error was thrown
when processing the class "AppBundleDataFixturesORMLoadCourseData": "Cl
ass DoctrineCommonDataFixturesAbstractFixture not found".
I would like to exclude the DataFixtures namespace from being autoloaded but I cannot find a way to do that.
php symfony composer-php symfony3.4 autoloader
add a comment |
I am using doctrine/data-fixtures
in dev environments and require it as follows:
composer.json:
"autoload": {
"psr-0": {
"": "src/",
"SymfonyStandard": "app/"
},
"classmap": [ "app/AppKernel.php", "app/AppCache.php" ]
},
"require-dev": {
"symfony/maker-bundle": "^1.8",
"phpunit/phpunit": "^7.0",
"doctrine/data-fixtures": "dev-rfc1872 as v1.2.1",
"doctrine/doctrine-fixtures-bundle": "^3.0"
},
In my Symfony 3.4 application my data fixtures live in /src/AppBundle/DataFixtures/ORM/*.php
.
When I run composer, which in turn runs a Symfony cache:clear I get the following error:
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'"
command:
In DefinitionErrorExceptionPass.php line 37:
While discovering services from namespace "AppBundle", an error was thrown
when processing the class "AppBundleDataFixturesORMLoadCourseData": "Cl
ass DoctrineCommonDataFixturesAbstractFixture not found".
I would like to exclude the DataFixtures namespace from being autoloaded but I cannot find a way to do that.
php symfony composer-php symfony3.4 autoloader
I am using doctrine/data-fixtures
in dev environments and require it as follows:
composer.json:
"autoload": {
"psr-0": {
"": "src/",
"SymfonyStandard": "app/"
},
"classmap": [ "app/AppKernel.php", "app/AppCache.php" ]
},
"require-dev": {
"symfony/maker-bundle": "^1.8",
"phpunit/phpunit": "^7.0",
"doctrine/data-fixtures": "dev-rfc1872 as v1.2.1",
"doctrine/doctrine-fixtures-bundle": "^3.0"
},
In my Symfony 3.4 application my data fixtures live in /src/AppBundle/DataFixtures/ORM/*.php
.
When I run composer, which in turn runs a Symfony cache:clear I get the following error:
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'"
command:
In DefinitionErrorExceptionPass.php line 37:
While discovering services from namespace "AppBundle", an error was thrown
when processing the class "AppBundleDataFixturesORMLoadCourseData": "Cl
ass DoctrineCommonDataFixturesAbstractFixture not found".
I would like to exclude the DataFixtures namespace from being autoloaded but I cannot find a way to do that.
php symfony composer-php symfony3.4 autoloader
php symfony composer-php symfony3.4 autoloader
asked Nov 22 '18 at 8:04
crmpiccocrmpicco
8,3391787153
8,3391787153
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I think you don't want to exclude data fixtures from being autoloaded, because they are valid PHP classes.
This error comes from Symfony's autowiring feature. So I assume you're indeed using autowiring.
You should data fixtures from autowiring discovery, which can be done in services.yml
with exclude
option.
Assuming you have something like (which should be there by default):
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository}'
All you need to do is to add DataFixtures
namespace to exclude
:
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository,DataFixtures}'
You can read more about it in here nad here
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426339%2fexcluding-data-fixtures-for-being-autloaded-by-composer-in-a-symfony-3-4-applica%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you don't want to exclude data fixtures from being autoloaded, because they are valid PHP classes.
This error comes from Symfony's autowiring feature. So I assume you're indeed using autowiring.
You should data fixtures from autowiring discovery, which can be done in services.yml
with exclude
option.
Assuming you have something like (which should be there by default):
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository}'
All you need to do is to add DataFixtures
namespace to exclude
:
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository,DataFixtures}'
You can read more about it in here nad here
add a comment |
I think you don't want to exclude data fixtures from being autoloaded, because they are valid PHP classes.
This error comes from Symfony's autowiring feature. So I assume you're indeed using autowiring.
You should data fixtures from autowiring discovery, which can be done in services.yml
with exclude
option.
Assuming you have something like (which should be there by default):
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository}'
All you need to do is to add DataFixtures
namespace to exclude
:
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository,DataFixtures}'
You can read more about it in here nad here
add a comment |
I think you don't want to exclude data fixtures from being autoloaded, because they are valid PHP classes.
This error comes from Symfony's autowiring feature. So I assume you're indeed using autowiring.
You should data fixtures from autowiring discovery, which can be done in services.yml
with exclude
option.
Assuming you have something like (which should be there by default):
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository}'
All you need to do is to add DataFixtures
namespace to exclude
:
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository,DataFixtures}'
You can read more about it in here nad here
I think you don't want to exclude data fixtures from being autoloaded, because they are valid PHP classes.
This error comes from Symfony's autowiring feature. So I assume you're indeed using autowiring.
You should data fixtures from autowiring discovery, which can be done in services.yml
with exclude
option.
Assuming you have something like (which should be there by default):
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository}'
All you need to do is to add DataFixtures
namespace to exclude
:
AppBundle:
resource: '../../src/AppBundle/*'
exclude: '../../src/AppBundle/{Entity,Repository,DataFixtures}'
You can read more about it in here nad here
answered Nov 22 '18 at 8:37
Jakub MatczakJakub Matczak
12k43449
12k43449
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426339%2fexcluding-data-fixtures-for-being-autloaded-by-composer-in-a-symfony-3-4-applica%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown