| Date | Commit message (Collapse) |
|---|
|
This release adds callback support to the Msgthr#add method,
allowing callers to track progress and potentially group
message. Thanks to Dimid Duchovny for this feature.
Discussion about it begins here:
https://80x24.org/msgthr-public/CANKvuDf7esPfy3eQ0B8aQjg4sTYTcxR_LNNWeDBcENFwmyC_3g@mail.gmail.com/t/
4 changes from Dimid Duchovny:
add callback to Msgthr#add
test: add a more complex test for add_child callback
test: fix add_child callback test
doc: document block parameter of Msgthr#add
|
|
This release simplifies the API to avoid (and raise on) user
errors. If your code worked with previous versions, there
are no changes necessary to make.
This release fixes our API to match the documentation in making
Msgthr#order! optional. Furthermore, the block previously
passed to Msgthr#order! may now be passed to Msgthr#thread!
instead.
For users who truly do not care about ordering, Msgthr#walk_thread
may be called immediately after the last call to Msgthr#add.
Thanks to Dimid Duchovny for the feedback which led to this release:
https://80x24.org/msgthr-public/CANKvuDc2mkxLuh+3+WXWfMXzxK2bShNesrD5xLocGOD1RybbwQ@mail.gmail.com/
|
|
.olddoc.yml requires the rdoc_url to point to the top-level
for NEWS, unfortunately; but attempt to reduce the indirection
in the main README. While we're at it, attempt to use the
metadata field in newer Rubygems.
|
|
|
|
Seems to work...
|
|
Mainly, we want to emphasize the container-agnosticism over the
non-recursive nature of our algorithm; as the former will likely
be more appealing to those not familiar with message threading
at all.
|
|
|