-
-
Notifications
You must be signed in to change notification settings - Fork 198
Conversation
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.
Those TODOS need to be fixed before merging tho
Probably fixed TODOS before merging is impossible. They depends from other sonata bundles. I can remove them but this will suspended tests. I think better keep it working becouse they show deprecations and bugs (like this TODOS) which should be fixed. |
Better to have something working |
@@ -11,10 +11,10 @@ | |||
* file that was distributed with this source code. | |||
*/ | |||
|
|||
namespace Sonata\Bundle\QABundle\Tests; | |||
namespace Tests\Sonata\Bundle\QABundle; |
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.
Would prefer Sonata\Tests
over Tests\Sonata
because the vendor is Sonata
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 want create sandbox as predefine application, ready to use where people can modify them. I replace tests becouse it is default directory for it. I think will be nice use Tests\Sonata
without Bundle\QABundle
, mybe even split it to seperate namespace like Tests\Sonata\News
. I prefer using Test\Sonata
becouse people can delete them without change in composer.json (this change require use composer update
).
"autoload-dev": {
"psr-4": {
"Tests\\": "tests/"
}
},
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.
BTW, should we merge QABundle with DemoBundle?
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.
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 want avoid modify composer.json becouse if people delete tests then they have to remove it from composer.json too and run composer update
to clear it on vendor/composer files.
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.
IMO having standard composer .json namespaces is better.
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.
IMO files from vendor directory should be trait as sonata files. Files from other directory should be trait as people files to keep it as easy is possible to edit. I dont think user will want edit composer after remove files.
@VincentLanglet What when someone add own tests? Then namespace Sonata\Tests
will be require.
@VincentLanglet @core23 @jordisala1991 WDYT?
My sugestion is:
- move AppBundle to src (App)
- move QABundle to DemoBundle
- split DemoBundle to DemoBundle and sonata-project instalator packege/bundle
- improve DemoBundle
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.
[...] if people delete tests then they have to remove it from composer.json too and run
composer update
to clear it on vendor/composer files.
This is a sandbox project. We should risk this and follow vendor-prefixed namespaces (Sonata\Tests
).
RTM |
@core23 @VincentLanglet Can you recheck it? |
Thank you @wbloszyk |
This PR will allow run phpunit test by: