-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fix path inconsistencies #34
base: master
Are you sure you want to change the base?
Conversation
FixtureController.php
Outdated
/** | ||
* @var string Alias to the fixture data path, where data files should be written. | ||
*/ | ||
public $fixtureDataPath = '@tests/unit/fixtures/data'; | ||
public $fixtureDataPath = '@tests/fixtures/data'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this would be breaking BC, can we fix overall consistency without BC break? And change the Paths in version 2.1 to be independent from unit tests then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could hardcode the former fixtureDataPath
value into the config/console.php
configuration file of the yii2-app-basic
template:
Like this:
'controllerMap' => [
'fixture' => [ // Fixture generation command line.
'class' => 'yii\faker\FixtureController',
'fixtureDataPath' => '@tests/unit/fixtures/data',
],
],
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ricpelo won't help since app templates are never updated in existing projects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@samdark You're right. Maybe we could do it for Yii 2.1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can release 2.1 version of the extension and note that it has backwards incompatibilities.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That could be great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@samdark May I need to create another PR, this time against 2.1 branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
@samdark I've just updated the PR so it's now against |
Fixes #33.