On Fri, May 1, 2020 at 3:09 PM David Bremner wrote:
> Ciprian Dorin Craciun writes:
> > I know that one can use `thread:{id:MESSAGE_ID}` to achieve the same
> > result, however:
> > * it is somewhat cumbersome for the integrator;
>
> Out of curiousity, what is harder about it? In both cases you h
David Bremner writes:
> Offhand I have no strong objection to someone (who is not me) adding
> this. I think it's important to be aware that thread id's are ephemeral,
> and subject to change e.g. if the database is re-built from
> scratch.
I guess a more common/interesting case is that two thre
Ciprian Dorin Craciun writes:
> I know that one can use `thread:{id:MESSAGE_ID}` to achieve the same
> result, however:
> * it is somewhat cumbersome for the integrator;
Out of curiousity, what is harder about it? In both cases you have to
extra one value from the JSON.
> * having the thread id
According to the `devel/schemata` the message object doesn't contain
the thread identifier to which it was assigned in the database.
Sometimes, for example in an UI that displays a search result at
message level, it would be useful to know the thread each message
belongs to, so the user can easily
