Extend protect/2 to accept a list of behviour modules

[camilleryr]

My team loves Hammox since it was recommended to us by Jose - and we really
appreciate all of the work you have put into it!

We often write modules that implement multiple behaviours and have gotten into
the habit of doing something similar to this in many of our tests

  setup_all do
    Map.merge(
      Hammox.protect(My.Module, My.Module.Contract),
      Hammox.protect(My.Module, My.Module.OtherContract)
    )
  end

This PR extends the api to Hammox.protect to be able to take in an
implementation module and a list of behaviours so that we could replace the
above with

  setup_all do
    Hammox.protect(My.Module, [My.Module.Contract, My.Module.OtherContract]),
  end

Please let me know if you have ideas of alternative implementations for this,
or if this does not fit with your design, feel free to disregard!

Once again - thanks for all of your work on this library - it has been very
valuable to our application!

[msz]

Sorry, I missed this!

I think that's a great idea. Mox also supports defining mocks for multiple behaviours so it only makes sense to mirror that API.

I'll look at the PR in more detail later!

In the meantime, have you considered using Hammox.Protect? It might make your use case just a bit neater:

use Hammox.Protect, module: My.Module, behaviour: My.Module.Contract
use Hammox.Protect, module: My.Module, behaviour: My.Module.OtherContract

In fact, as we do your proposed change, we could also do it for Hammox.Protect like this:

use Hammox.Protect, module: My.Module, behaviour: My.Module.Contract, behaviour: My.Module.OtherContract

[camilleryr]

Sorry, I missed this!

I think that's a great idea. Mox also supports defining mocks for multiple behaviours so it only makes sense to mirror that API.

I'll look at the PR in more detail later!

In the meantime, have you considered using Hammox.Protect? It might make your use case just a bit neater:

use Hammox.Protect, module: My.Module, behaviour: My.Module.Contract
use Hammox.Protect, module: My.Module, behaviour: My.Module.OtherContract

In fact, as we do your proposed change, we could also do it for Hammox.Protect like this:

use Hammox.Protect, module: My.Module, behaviour: My.Module.Contract, behaviour: My.Module.OtherContract

Thanks! I love that suggestion, I added another commit to this PR that allows for the usage of multiple behaviours in use Hammox.Protect as well (the options normalization is a bit hinkey, let me know if you have any thoughts!)

[msz]

Thank you, and sorry for taking so long to get back to you!