-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature composer config #2
base: main
Are you sure you want to change the base?
Conversation
- Add scripts to execute unit and functional tests. - Remove "typo3/cms-core" from extension dependencies. - Use distribution version of TYPO3 source for development. - Add support info.
Introduce namespace.
Specify global namespace prefix to tx_t3deploy_databaseController class.
composer.json
Outdated
"[ -e '.Build/bin/phpunit' ] || composer update", | ||
"TYPO3_PATH_ROOT=$(pwd)/.Build/Web .Build/bin/phpunit --colors -c .Build/vendor/nimut/testing-framework/res/Configuration/FunctionalTests.xml Tests/Functional" | ||
], | ||
"test:params": [ |
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.
Please remove this block. this was only for PoC in the composer meeting.
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.
It has been removed now.
Remove redundant configuration.
@@ -1,4 +1,6 @@ | |||
<?php | |||
namespace Aoe\t3deploy\Tests\Functional; |
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.
I would opt for UpperCamelCase in the namespace, thus Aoe\T3deploy\Tests\Functional.
Even though not being explicitly stated in PSR-4, this feels like an implicit convention to me, at least in the TYPO3 context.
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.
I realised this later. It has been fixed in "feature-implement-namespace" branch.
No description provided.