Once we can create new topics in the form of issues, refs #5, we want to reply to those issues by creating comments.
In this limited case, we can see comments and issues as forming a kind of meta-class called LETalk, with issues being a kind of container subclass of comments.
Realistically, comments can be attached to lots of classes we are simply not considering yet.
Therefore, we will have to make an architectural decision whether to have a set of keys the non-nil version of which tells what’s happening (as with UIViewController and friends) or to factor out the common “parent” object to which all comments can belong.
Once we can create new topics in the form of issues, refs #5, we want to reply to those issues by creating comments.
In this limited case, we can see comments and issues as forming a kind of meta-class called LETalk, with issues being a kind of container subclass of comments.
Realistically, comments can be attached to lots of classes we are simply not considering yet.
Therefore, we will have to make an architectural decision whether to have a set of keys the non-nil version of which tells what’s happening (as with UIViewController and friends) or to factor out the common “parent” object to which all comments can belong.