On Tue, May 1, 2012 at 6:19 PM, Alexey Panteleev <ale...@yoxel.com> wrote:
> Is the creator field not available anymore for a todo?
> Or there is another way to find out who created a todo?
This is an oversight -- thanks for reporting. We'll fix that up.
> On Tue, May 1, 2012 at 6:19 PM, Alexey Panteleev <ale...@yoxel.com> wrote:
>> Is the creator field not available anymore for a todo?
>> Or there is another way to find out who created a todo?
> This is an oversight -- thanks for reporting. We'll fix that up.
On Tue, May 1, 2012 at 8:41 PM, Alexey Panteleev <ale...@yoxel.com> wrote:
> Then probably also commentedAt? Comments_count would probably be enough to
> detect that a new comment was added, but the old api also had commentedAt.
> On Tue, May 1, 2012 at 8:41 PM, Alexey Panteleev <ale...@yoxel.com> wrote:
>> Then probably also commentedAt? Comments_count would probably be enough to
>> detect that a new comment was added, but the old api also had commentedAt.
> On Tue, May 1, 2012 at 8:41 PM, Alexey Panteleev <ale...@yoxel.com> wrote:
>> Then probably also commentedAt? Comments_count would probably be enough to
>> detect that a new comment was added, but the old api also had commentedAt.
On Wed, May 2, 2012 at 4:01 PM, Alexey Panteleev <ale...@yoxel.com> wrote:
> Are topics supposed to include 'creater' field?
> My first impression was that topic's id would be the same with its
> topicable's id but I guess they are separate objects in your db.
Anything that has one or more comments -- messages, to-dos, etc -- has
an associated topic. Internally, the topic aggregates comments,
attachments, and commenters, tracks latest timestamps, and provides an
excerpt of latest activity.
You could use topic.updated_at to replace your Classic API use of
todo.commented_at, for example.
The topic doesn't include a creator, though we could embed it with the
topicable (message, to-do, etc).
