(In reply to alexander :surkov from comment #16)
> (In reply to Ginn Chen from comment #15)
> > I think the solution is
> > 1) We implement both getNameCB and setNameCB, make sure setNameCB won't get
> > into getNameCB.
>
> makes sense to be on safe side. I'm fine with that.
seems good to me.
> > Same for parent, role, description, etc.
>
> I'd deal with them in follow ups. Otherwise it might be not a good first bug
> at all.
yeah, but each of them can probably be there own good first bug.
(In reply to alexander :surkov from comment #16)
> (In reply to Ginn Chen from comment #15)
> > I think the solution is
> > 1) We implement both getNameCB and setNameCB, make sure setNameCB won't get
> > into getNameCB.
>
> makes sense to be on safe side. I'm fine with that.
seems good to me.
> > Same for parent, role, description, etc.
>
> I'd deal with them in follow ups. Otherwise it might be not a good first bug
> at all.
yeah, but each of them can probably be there own good first bug.