Replace config(_:) to onActivate(_:)

[gmlwhdtjd]

The current implementation of config(:) is very simple and powerful.
However, this implementation sometimes results in unintended execution of the config block passed to config(:)
Also, because of the powerful implementation, it can sometimes be used in unintended ways.

So I created a new onActivate(_:) method, which solves the existing problem by storing the onActivate block in the view layout and deferring the execution of the block to the activation step.

[oozoofrog]

I cannot provide any justifiable reasons for this being disallowed.

[gmlwhdtjd]

I cannot provide any justifiable reasons for this being disallowed.

@oozoofrog
Actually, I'm not sure where layoutWillActivate() should be executed.

The way it is now, it's hard to add a method like layoutDidActivate() in the future, so we need to think about how to solve this problem and see if there is a better way.

[oozoofrog]

i don't have any reasons for this not allowed.

I cannot provide any justifiable reasons for this being disallowed.

@oozoofrog Actually, I'm not sure where layoutWillActivate() should be executed.

The way it is now, it's hard to add a method like layoutDidActivate() in the future, so we need to think about how to solve this problem and see if there is a better way.

may be we need create one or more sandboxing area in Activation for some lazy logics. we'll find a way. as always.