Add a property to the tracker history for all queries

[aryehb]

Closes #32

[felixmosh]

Thank you for the PR.
There is any which does the same thing...i think that will confuse people.

[Fryuni]

The difference is that history.any only holds queries matched using the on.any while history.all would have every query regardless of how it was matched.

For example:

tracker.on.insert('table_name').responseOnce(1);
tracker.on.update('table_name').responseOnce(1);

await knex.insert({id: 1, value: 1}).into('table_name').on_conflict('merge');

await knex.update({value: knex.raw('"value" + 1')}).from('table_name').where('id', 1);

// Contains only the insert
console.log(tracker.history.insert);

// Contains only the update
console.log(tracker.history.update);

// This one is empty
console.log(tracker.history.any);

// How to ensure that the update happened after the upsert?

[felixmosh]

For these places which you want to check order of exec, use the any matcher... Is it not enough?

[Fryuni]

Well... sure:

tracker.on.insert('table_name').responseOnce(1);
tracker.on.update('table_name').responseOnce(1);

// Could be replaced with
tracker.on.any(query => query.method === 'insert' && query.sql.includes('table_name')).responseOnce(1);
tracker.on.any(query => query.method === 'delete' && query.sql.includes('table_name')).responseOnce(1);

But this seems unnecessarily verbose.

[felixmosh]

Ok, You've convinced me, @aryehb let's fix the small things that I've mentioned, and we will merge it :]

[aryehb]

@felixmosh Can you clarify what you want me to change?

[felixmosh]

Rebase master
resetHistory should clean the all scope as well
Add some tests

[aryehb]

Ok, I'll work on those.

[aryehb]

@felixmosh I rebased and added the resetHistory() behavior, along with some tests. Let me know if there's any other tests you want me to add.

[felixmosh]

Thank you for this PR 🙏🏼
It released in v1.10.0