Thanks for this.
yes I can understand why it has never been a problem. It won’t be too
of a problem for us either, as the collection variable e.g. @tasks,
normally be filtered with .where() or be ordered with .order(),
they would be different instances. But I logged it as a bug, because it
just doesn’t seem right.
I can’t think of any reason why one would want the built instance added
the in memory collection…
Anyway, I think I’ve been a bit cheeky on the Github issue, not sure if
going to get another response!
Thanks for your reply though.