-
Notifications
You must be signed in to change notification settings - Fork 27
split up configuration into methods #246
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.
Do we need docblock for the sub-methods?
|
@dbu looks cool. Except my question about the docblocks, we can merge it. |
|
renamed the methods to configure... and added docblocks. |
|
The convention in Symfony core is to name these methods "addXxxSection" |
|
oh, ok. makes sense. i was looking at the doctrine bundle as inspiration. but addXxSection sounds good, will change to that |
|
and pushed again with the better names |
|
its awesome how big that configuration grews up. |
|
@dbu i just restarted the job, cause i don't understand the reason. The test failed just on php 5.6 and Symfony 2.3.* |
|
whaat was the change? |
split up configuration into methods
|
thanks @dbu |
|
no change. just restarted once more. no idea how that happened. |
i want to improve on #245 but notice that the configuration being one huge spaghetti is starting to get into the way. this PR changes no functionality at all, just splits the configuration tree building into separate sections. can we do this? then i will rebase #245 and try to push validation into the configuration definition.