is it suitable to control the component's state by the action passed by the parent component? about componentkit HOT 4 CLOSED

I have got the the answer, but i don't know if it's the best practice.

while the ParentComponent can reference the ChildComponent by the property nextResponder of sender. sender.nextResponder just point the ChildComponent

- (void)someAction:(CKComponent *)sender
{
  [sender.nextResponder updateState:^id(id) {
        return newState;
    }];
}

from componentkit.

Use two different actions:

@implementation ParentComponent

+ (instancetype)new
{
  return [super newWithComponent:
          [ChildComponent
           newWithAction:@selector(someAction:)]];
}

- (void)someAction:(CKComponent *)sender
{
  // Do something
}

@end

@implementation ChildComponent
{
  CKComponentAction _action;
}

+ (instancetype)newWithAction:(CKComponentAction)action
{
  ChildComponent *c =
  [super newWithComponent:
   [CKButtonComponent
    newWithAction:@selector(buttonAction)]];
  if (c) {
    c->_action = action;
  }
  return c;
}

- (void)buttonAction
{
  CKComponentActionSend(_action, self);
}

@end

from componentkit.

Since I just spent some time figuring this out, I might as well share the insight: This only seems to work if the child component has a custom ComponentController implementation (which can be completely empty!). Otherwise, I get an exception:

'NSInternalInconsistencyException', reason: 'Unhandled component action myAction: following responder chain <MyComponent: 0x7feeab1e81e0> -> nil'

I can't judge if this is a bug or as designed ;)

Edit: it turns out, this is only the case if you do an updateState before calling the passed action.

from componentkit.

@leoschweizer It works ok for me . By the way do your child component hold it's own state? if the component has no state, but you call the [childComponent updateState]. It will crash . You can review the doc http://componentkit.org/docs/state.html

from componentkit.