Remove all behaviors from the core #369

Closed
willdurand opened this Issue May 11, 2013 · 9 comments

Comments

Projects
None yet
9 participants
Owner

willdurand commented May 11, 2013

I'd like to remove all behaviors from the core, and create separate projects for them.
Don't worry, they will still be part of the core as dependencies.

The idea is to have a lighter core, and decouple behaviors from the core. That would ease maintenance. The only drawback I see is about the test suite. Behaviors related tests are useful.

WDYT?

Member

cristianoc72 commented May 11, 2013

Nice idea for me. We could also take the opportunity to think about a test
suite refactor.

2013/5/11 William Durand notifications@github.com

I'd like to remove all behaviors from the core, and create separate
projects for them.
Don't worry, they will still be part of the core as dependencies.

The idea is to have a lighter core, and decouple behaviors from the core.
That would ease maintenance. The only drawback I see is about the test
suite. Behaviors related tests are useful.

WDYT?


Reply to this email directly or view it on GitHubhttps://github.com/propelorm/Propel2/issues/369
.

Member

hhamon commented May 11, 2013

I'm really +1 for this.

Member

staabm commented May 11, 2013

👍 , maybe we could manage it like symfony handles its components (all source in one place and a subtree-split for the separation)

Contributor

gossi commented Jul 25, 2013

+1

If behaviors are installed via composer, then add them to the composer.json and run composer install before running the testsuite, which should do the trick?

Member

jaugustin commented Jul 25, 2013

tests are the main issue here because core behaviors have impact on each other, they all work well alone but together they could blow up :)

I am ok for the separation but we need to have a test project that test all core behavior in a complex environnement, and have unit test for each behavior in there repo

Agree,

Agree too for the tests, behaviors association is very useful.

Member

fzaninotto commented Jul 26, 2013

IMHO, this is another useless refactoring that delays the release of Propel2 by several months. No offense, but you should really focus on shipping the damn thing.

Owner

marcj commented Mar 8, 2014

-1 here

Owner

willdurand commented Mar 16, 2014

ok, let's forget this.

@willdurand willdurand closed this Mar 16, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment